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: <176268787124.581844.15968812562799652549.b4-ty@kernel.org>
Date: Sun, 09 Nov 2025 06:31:11 -0500
From: Leon Romanovsky <leon@...nel.org>
To: linux-kernel@...r.kernel.org, linux-rdma@...r.kernel.org, 
 Marco Crivellari <marco.crivellari@...e.com>
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>, Sagi Grimberg <sagi@...mberg.me>, 
 Max Gurtovoy <mgurtovoy@...dia.com>, Jason Gunthorpe <jgg@...pe.ca>
Subject: Re: [PATCH] IB/iser: add WQ_PERCPU to alloc_workqueue users


On Fri, 07 Nov 2025 14:33:06 +0100, Marco Crivellari wrote:
> Currently if a user enqueues a work item using schedule_delayed_work() the
> used wq is "system_wq" (per-cpu wq) while queue_delayed_work() use
> WORK_CPU_UNBOUND (used when a cpu is not specified). The same applies to
> schedule_work() that is using system_wq and queue_work(), that makes use
> again of WORK_CPU_UNBOUND.
> This lack of consistency cannot be addressed without refactoring the API.
> 
> [...]

Applied, thanks!

[1/1] IB/iser: add WQ_PERCPU to alloc_workqueue users
      https://git.kernel.org/rdma/rdma/c/65d21dee533755

Best regards,
-- 
Leon Romanovsky <leon@...nel.org>


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ