user/sven/linux.git/kernel/locking/rtmutex-debug.h, branch v3.14.54Linux Kernel
https://git.stealer.net/cgit.cgi/user/sven/linux.git/atom?h=v3.14.542014-07-01T03:11:58Zrtmutex: Handle deadlock detection smarter2014-07-01T03:11:58ZThomas Gleixnertglx@linutronix.de2014-06-05T10:34:23Zurn:sha1:fb52f40e085ef4074f1335672cd62c1f832af13b
commit 3d5c9340d1949733eb37616abd15db36aef9a57c upstream.
Even in the case when deadlock detection is not requested by the
caller, we can detect deadlocks. Right now the code stops the lock
chain walk and keeps the waiter enqueued, even on itself. Silly not to
yell when such a scenario is detected and to keep the waiter enqueued.
Return -EDEADLK unconditionally and handle it at the call sites.
The futex calls return -EDEADLK. The non futex ones dequeue the
waiter, throw a warning and put the task into a schedule loop.
Tagged for stable as it makes the code more robust.
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Brad Mouring <bmouring@ni.com>
Link: http://lkml.kernel.org/r/20140605152801.836501969@linutronix.de
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
locking: Move the rtmutex code to kernel/locking/2013-11-06T08:23:59ZPeter Zijlstrapeterz@infradead.org2013-10-31T17:18:19Zurn:sha1:1696a8bee390929fed05c6297164816ae2ced280
Suggested-by: Ingo Molnar <mingo@kernel.org>
Signed-off-by: Peter Zijlstra <peterz@infradead.org>
Link: http://lkml.kernel.org/n/tip-p9ijt8div0hwldexwfm4nlhj@git.kernel.org
[ Fixed build failure in kernel/rcu/tree_plugin.h. ]
Signed-off-by: Ingo Molnar <mingo@kernel.org>