Commit e3a55fd1 authored Mar 22, 2007 by Jarek Poplawski Committed by Linus Torvalds Mar 22, 2007

[PATCH] lockdep: lockdep_depth vs. debug_locks



lockdep found a bug during a run of workqueue function - this could be also
caused by a bug from other code running simultaneously.

lockdep really shouldn't be used when debug_locks == 0!

Reported-by: Folkert van Heusden <folkert@vanheusden.com>
Inspired-by: Oleg Nesterov <oleg@tv-sign.ru>
Signed-off-by: Jarek Poplawski <jarkao2@o2.pl>
Cc: Ingo Molnar <mingo@elte.hu>
Acked-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

parent 058560fb

include/linux/lockdep.h

+1 −1

Original line number	Diff line number	Diff line
		@@ -245,7 +245,7 @@ extern void lock_release(struct lockdep_map *lock, int nested,

		# define INIT_LOCKDEP .lockdep_recursion = 0,

		#define lockdep_depth(tsk) ((tsk)->lockdep_depth)
		#define lockdep_depth(tsk) (debug_locks ? (tsk)->lockdep_depth : 0)

		#else /* !LOCKDEP */

Admin message