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: <20220504080646.ypkpj7xc3rcgoocu@skbuf>
Date:   Wed, 4 May 2022 08:06:47 +0000
From:   Ioana Ciornei <ioana.ciornei@....com>
To:     Thorsten Leemhuis <regressions@...mhuis.info>
CC:     "davem@...emloft.net" <davem@...emloft.net>,
        "kuba@...nel.org" <kuba@...nel.org>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [regression] dpaa2: TSO offload on lx2160a causes fatal exception
 in interrupt

On Wed, May 04, 2022 at 09:46:49AM +0200, Thorsten Leemhuis wrote:
> Hi, this is your Linux kernel regression tracker.
> 
> Ioana, I noticed a regression report in bugzilla.kernel.org that afaics
> nobody acted upon since it was reported about a week ago. The reporter
> *suspects* it's caused by a recent change of yours. 

I was not aware of this regression report, thanks for letting me know.

> That's why I decided
> to forward it to the lists and all people that seemed to be relevant
> here. To quote from https://bugzilla.kernel.org/show_bug.cgi?id=215886
> 
> >  kernelbugs@...it.net 2022-04-25 18:15:38 UTC
> > 
> > Network traffic eventually causes a fatal exception in interrupt. Disabling TSO prevents the bug. Likely related to recent changes to enable TSO?
> > 
> > Crash:
> > 

<snip>

> > Mitigation:
> > ethtool -K ethX tso off
> > 
> > [reply] [−] Comment 1 kernelbugs@...it.net 2022-05-02 01:37:06 UTC
> > 
> > I believe this is related to commit 3dc709e0cd47c602a8d1a6747f1a91e9737eeed3
> > 
> 
> That commit is "dpaa2-eth: add support for software TSO".
> 
> Could somebody take a look into this? Or was this discussed somewhere
> else already? Or even fixed?

I will take a look at it, it wasn't discussed already.

Ioana

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ