diff options
author | Hillf Danton <hdanton@sina.com> | 2020-01-24 20:14:45 -0500 |
---|---|---|
committer | Tejun Heo <tj@kernel.org> | 2020-03-10 10:30:51 -0400 |
commit | aa202f1f56960c60e7befaa0f49c72b8fa11b0a8 (patch) | |
tree | 4666dc8751cd9751ac29f07b96e083ae9bb29f48 /crypto/async_tx/async_pq.c | |
parent | dbb92f88648d6206bf22fcb764fb9fe2939d401a (diff) |
workqueue: don't use wq_select_unbound_cpu() for bound works
wq_select_unbound_cpu() is designed for unbound workqueues only, but
it's wrongly called when using a bound workqueue too.
Fixing this ensures work queued to a bound workqueue with
cpu=WORK_CPU_UNBOUND always runs on the local CPU.
Before, that would happen only if wq_unbound_cpumask happened to include
it (likely almost always the case), or was empty, or we got lucky with
forced round-robin placement. So restricting
/sys/devices/virtual/workqueue/cpumask to a small subset of a machine's
CPUs would cause some bound work items to run unexpectedly there.
Fixes: ef557180447f ("workqueue: schedule WORK_CPU_UNBOUND work on wq_unbound_cpumask CPUs")
Cc: stable@vger.kernel.org # v4.5+
Signed-off-by: Hillf Danton <hdanton@sina.com>
[dj: massage changelog]
Signed-off-by: Daniel Jordan <daniel.m.jordan@oracle.com>
Cc: Tejun Heo <tj@kernel.org>
Cc: Lai Jiangshan <jiangshanlai@gmail.com>
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Tejun Heo <tj@kernel.org>
Diffstat (limited to 'crypto/async_tx/async_pq.c')
0 files changed, 0 insertions, 0 deletions