Messages in this thread | | | Date | Wed, 21 Mar 2007 21:16:35 +0300 | From | Oleg Nesterov <> | Subject | Re: [PATCH] Re: [2.6.20] BUG: workqueue leaked lock |
| |
On 03/21, Oleg Nesterov wrote: > > On 03/21, Jarek Poplawski wrote: > > > > So, if > > you have another idea for looking after it, let us know. > > No, I don't.
Perhaps we can add lockdep_depth() checks to laundromat_main/nfs4_laundromat to rule out workqueue.c. According to the trace, we return with client_mutex held, this seems impossible. So we can also print the value of mutex_is_locked() if lockdep_depth() != 0.
Oleg.
- 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/
| |