linux-kernel - Re: [PATCH] workqueue: Upgrade queue_work

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: <YaenioAmp10YJLrm@slm.duckdns.org>
Date:   Wed, 1 Dec 2021 06:49:14 -1000
From:   Tejun Heo <tj@...nel.org>
To:     "Paul E. McKenney" <paulmck@...nel.org>
Cc:     jiangshanlai@...il.com, linux-kernel@...r.kernel.org,
        frederic@...nel.org
Subject: Re: [PATCH] workqueue: Upgrade queue_work_on() comment

On Tue, Nov 30, 2021 at 05:00:30PM -0800, Paul E. McKenney wrote:
> The current queue_work_on() docbook comment says that the caller must
> ensure that the specified CPU can't go away, but does not spell out the
> consequences, which turn out to be quite mild.  Therefore expand this
> comment to explicitly say that the penalty for failing to nail down the
> specified CPU is that the workqueue handler might find itself executing
> on some other CPU.
> 
> Cc: Tejun Heo <tj@...nel.org>
> Cc: Lai Jiangshan <jiangshanlai@...il.com>
> Signed-off-by: Paul E. McKenney <paulmck@...nel.org>

Applied to wq/for-5.16-fixes.

Thanks.

-- 
tejun