netdev - Re: [PATCH net-next 5/6] dpaa

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20191021212248.0f2d5f57@cakuba.netronome.com>
Date:   Mon, 21 Oct 2019 21:22:48 -0700
From:   Jakub Kicinski <jakub.kicinski@...ronome.com>
To:     Madalin-cristian Bucur <madalin.bucur@....com>
Cc:     "davem@...emloft.net" <davem@...emloft.net>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        Roy Pledge <roy.pledge@....com>,
        Laurentiu Tudor <laurentiu.tudor@....com>
Subject: Re: [PATCH net-next 5/6] dpaa_eth: change DMA device

On Mon, 21 Oct 2019 12:28:02 +0000, Madalin-cristian Bucur wrote:
> The DPAA Ethernet driver is using the FMan MAC as the device for DMA
> mapping. This is not actually correct, as the real DMA device is the
> FMan port (the FMan Rx port for reception and the FMan Tx port for
> transmission). Changing the device used for DMA mapping to the Fman
> Rx and Tx port devices.
> 
> Signed-off-by: Madalin Bucur <madalin.bucur@....com>
> Signed-off-by: Laurentiu Tudor <laurentiu.tudor@....com>

Curious, we also have a patch for fixing this for IXP400.
Is there something in recent kernels that uncovers this bug?