lockdep: Print out additional debugging advice when we hit lockdep BUGs
authorDave Jones <davej@redhat.com>
Tue, 23 Apr 2013 16:34:03 +0000 (12:34 -0400)
committerIngo Molnar <mingo@kernel.org>
Fri, 26 Apr 2013 06:36:33 +0000 (08:36 +0200)
commit199e371f59d31c828345b0d959d27d752827b517
tree55d482c51276d98e2bcefba0b8460b48174f3e77
parentcc189d2513d1f45cde87a9043fe3be28559c7490
lockdep: Print out additional debugging advice when we hit lockdep BUGs

We occasionally get reports of these BUGs being hit, and the
stack trace doesn't necessarily always tell us what we need to
know about why we are hitting those limits.

If users start attaching /proc/lock_stats to reports we may have
more of a clue what's going on.

Signed-off-by: Dave Jones <davej@redhat.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Link: http://lkml.kernel.org/r/20130423163403.GA12839@redhat.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
kernel/lockdep.c