|author||Jonathan Corbet <email@example.com>||2011-04-22 11:19:10 -0600|
|committer||Ingo Molnar <firstname.lastname@example.org>||2011-04-24 13:18:38 +0200|
sched: Get rid of lock_depth
Neil Brown pointed out that lock_depth somehow escaped the BKL removal work. Let's get rid of it now. Note that the perf scripting utilities still have a bunch of code for dealing with common_lock_depth in tracepoints; I have left that in place in case anybody wants to use that code with older kernels. Suggested-by: Neil Brown <email@example.com> Signed-off-by: Jonathan Corbet <firstname.lastname@example.org> Cc: Arnd Bergmann <email@example.com> Cc: Peter Zijlstra <firstname.lastname@example.org> Cc: Thomas Gleixner <email@example.com> Cc: Linus Torvalds <firstname.lastname@example.org> Cc: Andrew Morton <email@example.com> Link: http://firstname.lastname@example.org Signed-off-by: Ingo Molnar <email@example.com>
Diffstat (limited to 'kernel/mutex.c')
1 files changed, 0 insertions, 7 deletions
diff --git a/kernel/mutex.c b/kernel/mutex.c
index fe4706cb0c5..2c938e2337c 100644
@@ -163,13 +163,6 @@ __mutex_lock_common(struct mutex *lock, long state, unsigned int subclass,
struct task_struct *owner;
- * If we own the BKL, then don't spin. The owner of
- * the mutex might be waiting on us to release the BKL.
- if (unlikely(current->lock_depth >= 0))
* If there's an owner, wait for it to either
* release the lock or go to sleep.