linux-kernel - Re: Shutdown-time hangs in -next in locktorture

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: <288a2295-fc1b-4a32-a3cf-990edc967655@paulmck-laptop>
Date: Sat, 20 Dec 2025 08:49:01 -0800
From: "Paul E. McKenney" <paulmck@...nel.org>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Ingo Molnar <mingo@...nel.org>, linux-kernel@...r.kernel.org,
	linux-next@...r.kernel.org, Stephen Rothwell <sfr@...b.auug.org.au>,
	Mark Brown <broonie@...nel.org>, kernel-team@...a.com
Subject: Re: Shutdown-time hangs in -next in locktorture

On Sat, Dec 20, 2025 at 01:52:01PM +0100, Peter Zijlstra wrote:
> On Fri, Dec 19, 2025 at 04:29:26PM -0800, Paul E. McKenney wrote:
> > Hello, Peter,
> > 
> > I started hitting shutdown-time hangs in next-20251217 which persist
> > in next-20251219.  This hang happens on both x86 and arm64.  Once I
> > figured out that the failure is high probability, but not deterministic,
> > bisection converged here:
> > 
> > 5d1f0b2f278e ("sched/core: Rework sched_class::wakeup_preempt() and rq_modified_*()")
> 
> That commit no longer exists in tip/sched/core; it was fixed a few days
> ago, except other problems made -next use an old tip branch which has
> caused this fix to have delayed visibility :-(

Very good, I will retry later.

							Thanx, Paul