linux-kernel - Re: [PATCH 0/4] Workqueue: replace system wq and change 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: <aKZYutvp4BtcqFJT@slm.duckdns.org>
Date: Wed, 20 Aug 2025 13:22:34 -1000
From: Tejun Heo <tj@...nel.org>
To: Marco Crivellari <marco.crivellari@...e.com>
Cc: linux-kernel@...r.kernel.org, Lai Jiangshan <jiangshanlai@...il.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Frederic Weisbecker <frederic@...nel.org>,
	Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
	Michal Hocko <mhocko@...e.com>
Subject: Re: [PATCH 0/4] Workqueue: replace system wq and change
 alloc_workqueue callers

Hello,

On Tue, Aug 19, 2025 at 10:41:01AM +0200, Marco Crivellari wrote:
> I'm not sure I have clearly understood what you mean here:
> 
> > e.g. Network flows through the same tree but different
> > filesystems often have their own trees.
> 
> With this, you mean also distinguish between e.g.  fs/ext4/  fs/etx2/
> and fs/btrfs/ etc?
> So if it is the case, in the example above, it means 3 different series.
> Prefixed like this, I imagine: "workqueue: btrfs: ....".

NVM, if Christian can apply for all filesystems, that's better.

> And I guess it would be the same for drivers, eg drivers/net/

I think net should be fine with wider scope patches, actually. It's mostly
about laying things out for respective subsys maintainers so that it's
easier for them to take actions.

Thanks.

-- 
tejun