linux-kernel - Re: Kernel WARNING (RCU) with btnxpuart on TI AM62 platform

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: <Z_Tt58Ar9TAUy4gB@gaggiata.pivistrello.it>
Date: Tue, 8 Apr 2025 11:35:35 +0200
From: Francesco Dolcini <francesco@...cini.it>
To: Paul Menzel <pmenzel@...gen.mpg.de>
Cc: Francesco Dolcini <francesco@...cini.it>,
	Amitkumar Karwar <amitkumar.karwar@....com>,
	Neeraj Kale <neeraj.sanjaykale@....com>, Nishanth Menon <nm@...com>,
	Tero Kristo <kristo@...nel.org>,
	Santosh Shilimkar <ssantosh@...nel.org>,
	linux-bluetooth@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org, linux-pm@...r.kernel.org,
	linux-serial@...r.kernel.org, regressions@...ts.linux.dev
Subject: Re: Kernel WARNING (RCU) with btnxpuart on TI AM62 platform

Hello,

On Tue, Apr 08, 2025 at 11:26:47AM +0200, Paul Menzel wrote:
> [Cc: +regressions@]
> 
> #regzbot introduced: v6.14..v6.15-rc1
> 
> 
> Thank you for your report.
> 
> Am 08.04.25 um 10:35 schrieb Francesco Dolcini:
> 
> > I do have the following kernel warning with 6.15-rc1, on a TI AM62
> > platform (arm64), single CPU core, using btnxpuart driver, any idea?
> > PREEMPT_RT is enabled, if it matters.
> > 
> > Either the issue is not systematic, or multi cores SoCs are not affected
> > (no error on the exact same image on a dual nor on quad core TI AM62).
> > 
> > 
> > [   23.139080] Voluntary context switch within RCU read-side critical section!
> > [   23.139119] WARNING: CPU: 0 PID: 61 at /kernel/rcu/tree_plugin.h:332 rcu_note_context_switch+0x3c4/0x430

...

> As I understood, that it’s a regression, and you can reproduce it, would it
> be possible, that you bisected the issue?

I am not sure if this is a regression. It's possible that the issue is not new,
and it is just non systematic. For sure it was reproduced by our CI on v6.15-rc1.

Francesco