linux-kernel - RE: [PATCH net 4/4] dpaa_eth: FMan erratum A050385 workaround

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] [day] [month] [year] [list]

Message-ID: <DB8PR04MB69853AF43BD3252FF06A57D0ECE50@DB8PR04MB6985.eurprd04.prod.outlook.com>
Date:   Wed, 4 Mar 2020 15:51:09 +0000
From:   "Madalin Bucur (OSS)" <madalin.bucur@....nxp.com>
To:     David Miller <davem@...emloft.net>,
        "Madalin Bucur (OSS)" <madalin.bucur@....nxp.com>
CC:     "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "robh+dt@...nel.org" <robh+dt@...nel.org>,
        "mark.rutland@....com" <mark.rutland@....com>,
        "shawnguo@...nel.org" <shawnguo@...nel.org>,
        Leo Li <leoyang.li@....com>,
        "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH net 4/4] dpaa_eth: FMan erratum A050385 workaround

> -----Original Message-----
> From: David Miller <davem@...emloft.net>
> Sent: Wednesday, March 4, 2020 1:54 AM
> To: Madalin Bucur (OSS) <madalin.bucur@....nxp.com>
> Subject: Re: [PATCH net 4/4] dpaa_eth: FMan erratum A050385 workaround
> 
> From: Madalin Bucur <madalin.bucur@....nxp.com>
> Date: Tue,  3 Mar 2020 17:55:39 +0200
> 
> > +#define DPAA_FD_DATA_ALIGNMENT  ((fman_has_errata_a050385()) ? \
> 
> You don't need parenthesis around that fman_has_errata_a050385() call.
> 
> > +#define dpaa_bp_size(raw_size) ((SKB_WITH_OVERHEAD(raw_size)) & \
> 
> Similar again for SKB_WITH_OVERHEAD()

I'll send a v2, thanks.
 
> Also, how often does this errata code trigger on effected platforms and
> what is the performance degradation from that?  I don't see this analysis
> performed anywhere.

To reproduce this issue when the workaround is not applied, one
needs to ensure the FMan DMA transaction queue is already full
when a transaction split occurs so the system must be under high
traffic load (i.e. multiple ports at line rate). After the errata
occurs, the traffic stops. The only SoC impacted by this is the
LS1043A, the other ARM DPAA 1 SoC or the PPC DPAA 1 SoCs do not
have this erratum.

Madalin