Received-SPF: pass (google.com: domain of linux-kernel+bounces-168501-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) client-ip=2604:1380:45e3:2400::1;
Sender: Tejun Heo <htejun@gmail.com>
Date: Fri, 3 May 2024 16:47:52 -1000
From: Tejun Heo <tj@kernel.org>
To: John Stultz <jstultz@google.com>
Cc: Lai Jiangshan <jiangshanlai@gmail.com>, Will Deacon <will@kernel.org>,
	Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	LKML <linux-kernel@vger.kernel.org>, kernel-team@android.com
Subject: Re: WW_MUTEX_SELFTEST hangs w/ 6.9-rc workqueue changes
Message-ID: <ZjWh2MbDs1CF8PUB@slm.duckdns.org>
References: <CANDhNCq2n2HVUnVi0K+cw_7MUd1h49BzTxLEk6V3G2c=BBUYBw@mail.gmail.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CANDhNCq2n2HVUnVi0K+cw_7MUd1h49BzTxLEk6V3G2c=BBUYBw@mail.gmail.com>

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