linux-kernel - Re: [Regression] wifi problems since tg3 started throwing rcu stall warnings

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: <ZyyQuTfMMSLwStf_@pavilion.home>
Date: Thu, 7 Nov 2024 11:04:41 +0100
From: Frederic Weisbecker <frederic@...nel.org>
To: Thorsten Leemhuis <regressions@...mhuis.info>
Cc: Mingcong Bai <jeffbai@...c.io>,
	Linux regressions mailing list <regressions@...ts.linux.dev>,
	LKML <linux-kernel@...r.kernel.org>,
	"Paul E. McKenney" <paulmck@...nel.org>, rcu <rcu@...r.kernel.org>,
	sakiiily@...c.io
Subject: Re: [Regression] wifi problems since tg3 started throwing rcu stall
 warnings

Le Thu, Nov 07, 2024 at 10:10:37AM +0100, Thorsten Leemhuis a écrit :
> On 05.11.24 08:17, Mingcong Bai wrote:
> > (CC-ing the laptop's owner so that she might help with further testing...)
> > 在 2024-10-23 18:22，Linux regression tracking (Thorsten Leemhuis) 写道：
> >> On 23.10.24 12:09, Frederic Weisbecker wrote:
> >>> Le Wed, Oct 23, 2024 at 10:27:18AM +0200, Linux regression tracking
> >>> (Thorsten Leemhuis) a écrit :
> >>>>
> >>>> Frederic, I noticed a report about a regression in bugzilla.kernel.org
> >>>> that appears to be caused by the following change of yours:
> >>>> 55d4669ef1b768 ("rcu: Fix rcu_barrier() VS post CPUHP_TEARDOWN_CPU
> >>>> invocation")
> >>> Are you sure about the commit? Below it says:
> >> Not totally, but...
> >>
> >>>> As many (most?) kernel developers don't keep an eye on the bug tracker,
> >>>> I decided to write this mail. To quote from
> >>>> https://bugzilla.kernel.org/show_bug.cgi?id=219390:
> >>>>
> >>>>>  Mingcong Bai 2024-10-15 13:32:35 UTC
> >>>>> Since aa162aa4aa383a0a714b1c36e8fcc77612ddd1a2 between v6.10.4 and
> >>> Now that's aa162aa4aa383a0a714b1c36e8fcc77612ddd1a2 which I can't
> >>> find in vanilla
> >>> tree.
> >> ...quite, as that is the commit-id of the backport to v6.10.5; and the
> >> reporter reverted it there. Ideally of course that would have happened
> >> on recent mainline. If you doubt, ask Mingcong Bai to check if a revert
> >> there helps, too.
> > Do we need any further information/testing on this issue? Please let me
> > know if there's anything we can do as the issue still persists in 6.12.
> 
> Hmm, no reply from Frederic. Not sure why, maybe he is just away from
> the keyboard for a few days. But if the reporter has a minute, it might
> be wise to check if reverting that commit on top of 6.12-rc6 or newer
> also fixes the problem, to rule out any interference from changes
> specific to the stable series.
> 
> Ciao, Thorsten

Sorry for the lag, I still don't understand how this specific commit
can produce this issue. Can you please retry with and without this commit
reverted?

Thanks.