linux-kernel - Re: [PATCH 5/7 V2] workqueue: reuse the current default pwq when its attrs unchanged

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]

Date:	Mon, 18 May 2015 16:38:09 -0400
From:	Tejun Heo <tj@...nel.org>
To:	Lai Jiangshan <laijs@...fujitsu.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 5/7 V2] workqueue: reuse the current default pwq when its
 attrs unchanged

Hello,

On Tue, May 12, 2015 at 08:32:33PM +0800, Lai Jiangshan wrote:
> When apply_wqattrs_prepare() is called, it is possible that the default
> pwq is unaffected.  It is always true that only the NUMA affinity is being
> changed and sometimes true that the low level cpumask is being changed.
> 
> So we try to reuse the current default pwq when its attrs unchanged.
> 
> After this change, "ctx->dfl_pwq->refcnt++" could be dangerous
> when ctx->dfl_pwq is being reused, so we use get_pwq_unlocked() instead.

Can you elaborate the above paragraph?  Why wouldn't that be dangerous
before this change?

Thanks.

-- 
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/