linux-kernel - Re: [PATCH 05/11 V5] workqueue: Add @bind arguement back without change any thing

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:	Wed, 5 Sep 2012 12:49:08 -0700
From:	Tejun Heo <tj@...nel.org>
To:	Lai Jiangshan <laijs@...fujitsu.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 05/11 V5] workqueue: Add @bind arguement back without
 change any thing

Hello,

On Wed, Sep 05, 2012 at 06:37:42PM +0800, Lai Jiangshan wrote:
> Ensure the gcwq->flags is only accessed with gcwq->lock held.
> And make the code more easier to understand.
>
> In all current callsite of create_worker(), DISASSOCIATED can't
> be flipped while create_worker().
> So the whole behavior is unchanged with this patch.

This doesn't change anything.  You're just moving the test to the
caller with comments there explaining how it won't change even if
gcwq->lock is released.  It seems more confusing to me.  The flag is
still protected by manager_mutex.  How is this an improvement?

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/