From: Lai Jiangshan <laijs@cn.fujitsu.com>
To: Tejun Heo <tj@kernel.org>
Cc: <linux-kernel@vger.kernel.org>,
"Jason J. Herne" <jjherne@linux.vnet.ibm.com>,
Sasha Levin <sasha.levin@oracle.com>
Subject: Re: [PATCH 2/2] workqueue: stronger test in process_one_work()
Date: Thu, 26 Jun 2014 19:27:43 +0800 [thread overview]
Message-ID: <53AC03AF.9050303@cn.fujitsu.com> (raw)
In-Reply-To: <20140619194432.GC7390@mtj.dyndns.org>
On 06/20/2014 03:44 AM, Tejun Heo wrote:
> On Tue, Jun 03, 2014 at 03:33:28PM +0800, Lai Jiangshan wrote:
>> When POOL_DISASSOCIATED is cleared, the running worker's local CPU should
>> be the same as pool->cpu without any exception even during cpu-hotplug.
>>
>> This fix changes "(proposition_A && proposition_B && proposition_C)"
>> to "(proposition_B && proposition_C)", so if the old compound proposition
>> is true, the new one must be true too. so this fix will not hide any
>> possible bug which can be hit by old test.
>>
>> CC: Jason J. Herne <jjherne@linux.vnet.ibm.com>
>> CC: Sasha Levin <sasha.levin@oracle.com>
>> Signed-off-by: Lai Jiangshan <laijs@cn.fujitsu.com>
>
> Applied to wq/for-3.17 with minor updates.
>
> Nice set of cleanups. Thanks!
>
Hi,Tejun
I found the slight earlier 6 patches are in wq/for-3.17.
But these two patches (in this email thread) are not in wq/for-3.17 yet.
workqueue: clear POOL_DISASSOCIATED in rebind_workers()
workqueue: stronger test in process_one_work()
Thanks,
Lai
next prev parent reply other threads:[~2014-06-26 11:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 7:33 [PATCH 1/2] workqueue: clear POOL_DISASSOCIATED in rebind_workers() Lai Jiangshan
2014-06-03 7:33 ` [PATCH 2/2] workqueue: stronger test in process_one_work() Lai Jiangshan
2014-06-19 19:44 ` Tejun Heo
2014-06-26 11:27 ` Lai Jiangshan [this message]
2014-06-30 2:32 ` Lai Jiangshan
2014-07-01 21:41 ` Tejun Heo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53AC03AF.9050303@cn.fujitsu.com \
--to=laijs@cn.fujitsu.com \
--cc=jjherne@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sasha.levin@oracle.com \
--cc=tj@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).