linux-kernel - Re: [PATCH 3/5] workqueue: fixup existing pool->node

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: <20141225201406.GB22951@htj.dyndns.org>
Date:	Thu, 25 Dec 2014 15:14:06 -0500
From:	Tejun Heo <tj@...nel.org>
To:	Lai Jiangshan <laijs@...fujitsu.com>
Cc:	linux-kernel@...r.kernel.org,
	Yasuaki Ishimatsu <isimatu.yasuaki@...fujitsu.com>,
	"Gu, Zheng" <guz.fnst@...fujitsu.com>,
	tangchen <tangchen@...fujitsu.com>,
	Hiroyuki KAMEZAWA <kamezawa.hiroyu@...fujitsu.com>
Subject: Re: [PATCH 3/5] workqueue: fixup existing pool->node

On Mon, Dec 15, 2014 at 09:23:49AM +0800, Lai Jiangshan wrote:
> The pwqs of the old node's cpumask do be discarded. But the pools of the old
> node's cpumask maybe recycle. For example, a new workqueue's affinity is set to
> the old node's cpumask before the pool is dead. Any old pool can long live.

Hah?  Why can't it just be unhashed so that it can't be looked up for
new pwqs anymore?

-- 
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/