linux-kernel - Re: [PATCH 1/1] wifi: libertas: WQ_PERCPU added to alloc

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <b64db199e6e1cd09b26f44d2e8cc1bec43b163fd.camel@sipsolutions.net>
Date: Mon, 22 Sep 2025 13:33:09 +0200
From: Johannes Berg <johannes@...solutions.net>
To: Marco Crivellari <marco.crivellari@...e.com>, 
	linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org
Cc: Tejun Heo <tj@...nel.org>, Lai Jiangshan <jiangshanlai@...il.com>, 
 Frederic Weisbecker	 <frederic@...nel.org>, Sebastian Andrzej Siewior
 <bigeasy@...utronix.de>,  Michal Hocko <mhocko@...e.com>, Francesco Dolcini
 <francesco.dolcini@...adex.com>, Brian Norris	 <briannorris@...omium.org>,
 Sascha Hauer <s.hauer@...gutronix.de>, Kalle Valo	 <kvalo@...nel.org>, "Dr
 . David Alan Gilbert" <linux@...blig.org>, Jeff Chen	
 <jeff.chen_1@....com>, Stefan Kerkmann <s.kerkmann@...gutronix.de>
Subject: Re: [PATCH 1/1] wifi: libertas: WQ_PERCPU added to alloc_workqueue
 users

On Mon, 2025-09-22 at 12:24 +0200, Marco Crivellari wrote:
> 
> With the introduction of the WQ_PERCPU flag (equivalent to !WQ_UNBOUND),
> any alloc_workqueue() caller that doesn’t explicitly specify WQ_UNBOUND
> must now use WQ_PERCPU.

Which I guess forces a decision, and should be kept for a few releases,
but ... is "keep what it did" really the right decision in all places?
It seems to me that for instance for libertas here, there really is no
reason to be CPU bound?

johannes