Re: [PATCH] workqueue: fix potential reentrancy issue

2013-09-09 Thread Libin
Hello Tejun, On 2013/9/9 22:14, Tejun Heo wrote: > On Mon, Sep 09, 2013 at 01:12:14PM +0800, Libin wrote: >> From: Li Bin >> >> When one work starts execution, the high bits of work's data contain >> pool ID. It can represent a maximum of WORK_OFFQ_POOL_NONE. Pool ID >> is assigned WORK_OFFQ_POOL_

Re: [PATCH] workqueue: fix potential reentrancy issue

2013-09-09 Thread Tejun Heo
On Mon, Sep 09, 2013 at 01:12:14PM +0800, Libin wrote: > From: Li Bin > > When one work starts execution, the high bits of work's data contain > pool ID. It can represent a maximum of WORK_OFFQ_POOL_NONE. Pool ID > is assigned WORK_OFFQ_POOL_NONE when the work being initialized > indicating that

[PATCH] workqueue: fix potential reentrancy issue

2013-09-08 Thread Libin
From: Li Bin When one work starts execution, the high bits of work's data contain pool ID. It can represent a maximum of WORK_OFFQ_POOL_NONE. Pool ID is assigned WORK_OFFQ_POOL_NONE when the work being initialized indicating that no pool is associated and get_work_pool() uses it to check the asso