Messages in this thread | | | Date | Thu, 22 Mar 2007 08:23:02 +0100 | From | Jarek Poplawski <> | Subject | Re: [PATCH] lockdep: lockdep_depth vs. debug_locks Re: [2.6.20] BUG: workqueue leaked lock |
| |
On Thu, Mar 22, 2007 at 08:06:44AM +0100, Jarek Poplawski wrote: ... > This should definitely solve this problem - as it was said > a few times before lockdep stops registering locks after > a bug, so even the lock which caused the warning isn't > reported. Here lockdep found a bug in a workqueue function,
More precisely:
lockdep found a bug during a run of workqueue function - this could be also caused by a bug from other code running simultaneusly.
Jarek P. - 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/
| |