linux-kernel - Re: [PATCH] workqueue: Fix pool->nr

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: <ZcL1SofG_uul0732@slm.duckdns.org>
Date: Tue, 6 Feb 2024 17:13:14 -1000
From: Tejun Heo <tj@...nel.org>
To: yunlong xing <yunlongxing23@...il.com>
Cc: Yunlong Xing <yunlong.xing@...soc.com>, jiangshanlai@...il.com,
	linux-kernel@...r.kernel.org, hongyu.jin@...soc.com,
	zhiguo.niu@...soc.com, zhengxu.zhang@...soc.com
Subject: Re: [PATCH] workqueue: Fix pool->nr_running type back to atomic

Hello,

On Wed, Feb 07, 2024 at 10:06:56AM +0800, yunlong xing wrote:
> Yes, WARN_ON is triggered. The reason of  set_cpus_allowed_ptr() fail  still
> needs to be further investigated.

I see. Please include context like the above when posting patches.

> I was originally planning to inquire workqueue whether or not allows the worker
> that associated with one cpu running on the other cpus？From your reply，the
> answer of my question is not allow，right？

Yes, you're right. set_cpus_allowed_ptr() shouldn't fail.

Thanks.

-- 
tejun