[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZjWh2MbDs1CF8PUB@slm.duckdns.org>
Date: Fri, 3 May 2024 16:47:52 -1000
From: Tejun Heo <tj@...nel.org>
To: John Stultz <jstultz@...gle.com>
Cc: Lai Jiangshan <jiangshanlai@...il.com>, Will Deacon <will@...nel.org>,
Ingo Molnar <mingo@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
LKML <linux-kernel@...r.kernel.org>, kernel-team@...roid.com
Subject: Re: WW_MUTEX_SELFTEST hangs w/ 6.9-rc workqueue changes
Hello, John.
On Fri, May 03, 2024 at 06:01:49PM -0700, John Stultz wrote:
> Hey All,
> In doing some local testing, I noticed I've started to see boot
> stalls with CONFIG_WW_MUTEX_SELFTEST with 6.9-rc on a 64cpu qemu
> environment.
>
> I've bisected the problem down to:
> 5797b1c18919 (workqueue: Implement system-wide nr_active enforcement
> for unbound workqueues)
> + the fix needed for that change:
> 15930da42f89 (workqueue: Don't call cpumask_test_cpu() with -1 CPU
> in wq_update_node_max_active())
This should be fixed by d40f92020c7a ("workqueue: The default node_nr_active
should have its max set to max_active"). Can you please confirm the fix?
Thanks and sorry about the hassle.
--
tejun
Powered by blists - more mailing lists