linux-kernel - Re: [PATCH] workqueue: Initialize wq_isolated_cpumask in workqueue_init

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: <aFG6-Jk4A7BwGmSU@slm.duckdns.org>
Date: Tue, 17 Jun 2025 08:59:04 -1000
From: Tejun Heo <tj@...nel.org>
To: Chuyi Zhou <zhouchuyi@...edance.com>
Cc: longman@...hat.com, jiangshanlai@...il.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] workqueue: Initialize wq_isolated_cpumask in
 workqueue_init_early()

On Tue, Jun 17, 2025 at 12:42:16PM +0800, Chuyi Zhou wrote:
> Now when isolcpus is enabled via the cmdline, wq_isolated_cpumask does
> not include these isolated CPUs, even wq_unbound_cpumask has already
> excluded them. It is only when we successfully configure an isolate cpuset
> partition that wq_isolated_cpumask gets overwritten by
> workqueue_unbound_exclude_cpumask(), including both the cmdline-specified
> isolated CPUs and the isolated CPUs within the cpuset partitions.
> 
> Fix this issue by initializing wq_isolated_cpumask properly in
> workqueue_init_early().
> 
> Fixes: fe28f631fa94 ("workqueue: Add workqueue_unbound_exclude_cpumask() to exclude CPUs from wq_unbound_cpumask")
> Signed-off-by: Chuyi Zhou <zhouchuyi@...edance.com>

Applied to wq/for-6.16-fixes.

Thanks.

-- 
tejun