linux-kernel - Re: [PATCH] sched_ext, rcu: Eject BPF scheduler on RCU CPU stall panic

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: <aFsvYhPTIyQWSFmL@slm.duckdns.org>
Date: Tue, 24 Jun 2025 13:06:10 -1000
From: Tejun Heo <tj@...nel.org>
To: David Dai <david.dai@...ux.dev>
Cc: void@...ifault.com, arighi@...dia.com, changwoo@...lia.com,
	paulmck@...nel.org, davidai@...a.com, sched-ext@...ts.linux.dev,
	linux-kernel@...r.kernel.org, rcu@...r.kernel.org,
	kernel-team@...a.com
Subject: Re: [PATCH] sched_ext, rcu: Eject BPF scheduler on RCU CPU stall
 panic

On Tue, Jun 24, 2025 at 03:49:06PM -0700, David Dai wrote:
> For systems using a sched_ext scheduler and has panic_on_rcu_stall
> enabled, try kicking out the current scheduler before issuing a panic.
> 
> While there are numerous reasons for RCU CPU stalls that are not
> directly attributed to the scheduler, deferring the panic gives
> sched_ext an opportunity to provide additional debug info when ejecting
> the current scheduler. Also, handling the event more gracefully allows
> us to potentially recover the system instead of incurring additional
> down time.
> 
> Suggested-by: Tejun Heo <tj@...nel.org>
> Reviewed-by: Paul E. McKenney <paulmck@...nel.org>
> Signed-off-by: David Dai <david.dai@...ux.dev>

Applied to sched_ext/for-6.17.

Thanks.

-- 
tejun