Messages in this thread |  | | | Date | Mon, 20 Dec 2010 17:21:10 +0100 | | From | Tejun Heo <> | | Subject | Re: [PATCH] kthread_worker: Initialize dynamically allocated spinlock properly for lockdep |
| |
Hello,
On 12/20/2010 10:28 AM, Yong Zhang wrote: > Subject: [PATCH] kthread_work: Make lockdep happy > > spinlock in kthread_worker and wait_queue_head in kthread_work > both should be lockdep annotated. > So change the interface to make it suiltable for CONFIG_LOCKDEP. > > Signed-off-by: Yong Zhang <yong.zhang0@gmail.com> > --- > I'm not sure if it's possible to define a worker on stack? > So I left DEFINE_KTHREAD_WORKER() untouched.
Yes, it can, I think. BTW, where are you using kthread_worker? I'm planning to update its flush semantics similar to that of proper workqueue so that it's less confusing and switching between the two is easy, so its usage may change slightly soon, although conversion shouldn't be difficult.
Thanks.
-- tejun
|  |