rtmutex: Warn if trylock is called from hard/softirq context
authorThomas Gleixner <tglx@linutronix.de>
Wed, 13 May 2015 20:49:12 +0000 (22:49 +0200)
committerThomas Gleixner <tglx@linutronix.de>
Wed, 13 May 2015 20:49:12 +0000 (22:49 +0200)
commit6ce47fd961fa8fb206433789d7754c73cab3b5d0
tree2d2526d43c95232bc14bd9228f02de8fa14bd3dc
parenta22e5f579b98f16e24b7184d01c35de26eb5a7f7
rtmutex: Warn if trylock is called from hard/softirq context

rt_mutex_trylock() must be called from thread context. It can be
called from atomic regions (preemption or interrupts disabled), but
not from hard/softirq/nmi context. Add a warning to alert abusers.

The reasons for this are:

    1) There is a potential deadlock in the slowpath

    2) Another cpu which blocks on the rtmutex will boost the task
       which allegedly locked the rtmutex, but that cannot work
       because the hard/softirq context borrows the task context.

Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Sebastian Siewior <bigeasy@linutronix.de>
kernel/locking/rtmutex.c
This page took 0.023754 seconds and 5 git commands to generate.