Date: Tue, 12 May 2015 09:19:41 -0400
From: Tejun Heo <tj@kernel.org>
To: Lai Jiangshan <laijs@cn.fujitsu.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/5] workqueue: ensure attrs-changing be sequentially
Message-ID: <20150512131941.GL11388@htj.duckdns.org>
References: <1431336953-3260-1-git-send-email-laijs@cn.fujitsu.com>
 <1431336953-3260-4-git-send-email-laijs@cn.fujitsu.com>
 <20150511145502.GD11388@htj.duckdns.org>
 <55518B1E.8010309@cn.fujitsu.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <55518B1E.8010309@cn.fujitsu.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1382
Lines: 42

Hello,

On Tue, May 12, 2015 at 01:09:50PM +0800, Lai Jiangshan wrote:
> On 05/11/2015 10:55 PM, Tejun Heo wrote:
> >>
> >> Process A (change cpumask)	| Process B (change numa affinity)
> >> wq_cpumask_store()		|
> >>   wq_sysfs_prep_attrs()		|
> > 				^
> > 				misaligned
> 
> It is aligned in email, misaligned in quoted email, and misaligned
> in `git log` and `git show`, aligned in `git commit` when I wrote
> the changelog. 
> 
> I will just remove all the |.

Hmmm... I wonder why that is.  It looks consistently misaligned here.
If in doubt, just use spaces instead of tabs when drawing stuff.

...
> >> Sequential model on non-performance-sensitive operations is more popular
> >> and preferred. So this patch moves wq_sysfs_prep_attrs() into the protection
> > 
> > You can just say the previous behavior is buggy.
> 
> It depends on definitions. To me, it is just a nuisance.

I find this pretty difficult to agree with.  A does an operation which
changes attribute 1.  B independently tries to change attribute 2.
Depending on the sequence, we end up with three different results.
How is this not a bug?

Thanks.

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