aboutsummaryrefslogtreecommitdiffstats
path: root/REPORTING-BUGS
diff options
context:
space:
mode:
authorSteven Rostedt <srostedt@redhat.com>2011-04-20 21:41:55 -0400
committerIngo Molnar <mingo@elte.hu>2011-04-22 11:06:57 +0200
commitf4185812aa046ecb97e8817e10148cacdd7a6baa (patch)
treea17a417d13586554f452df9fd251165c4d714a97 /REPORTING-BUGS
parent3003eba313dd0e0502dd71548c36fe7c19801ce5 (diff)
downloadkernel_samsung_smdk4412-f4185812aa046ecb97e8817e10148cacdd7a6baa.zip
kernel_samsung_smdk4412-f4185812aa046ecb97e8817e10148cacdd7a6baa.tar.gz
kernel_samsung_smdk4412-f4185812aa046ecb97e8817e10148cacdd7a6baa.tar.bz2
lockdep: Print a nicer description for normal deadlocks
The lockdep output can be pretty cryptic, having nicer output can save a lot of head scratching. When a normal deadlock scenario is detected by lockdep (lock A -> lock B and there exists a place where lock B -> lock A) we now get the following new output: other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(lockB); lock(lockA); lock(lockB); lock(lockA); *** DEADLOCK *** On cases where there's a deeper chair, it shows the partial chain that can cause the issue: Chain exists of: lockC --> lockA --> lockB Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(lockB); lock(lockA); lock(lockB); lock(lockC); *** DEADLOCK *** Signed-off-by: Steven Rostedt <rostedt@goodmis.org> Acked-by: Peter Zijlstra <a.p.zijlstra@chello.nl> Cc: Frederic Weisbecker <fweisbec@gmail.com> Cc: Linus Torvalds <torvalds@linux-foundation.org> Cc: Andrew Morton <akpm@linux-foundation.org> Link: http://lkml.kernel.org/r/20110421014259.380621789@goodmis.org Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'REPORTING-BUGS')
0 files changed, 0 insertions, 0 deletions