locking/rtmutex: Handle non enqueued waiters gracefully in remove_waiter()
authorPeter Zijlstra <peterz@infradead.org>
Tue, 27 Mar 2018 12:14:38 +0000 (14:14 +0200)
committerThomas Gleixner <tglx@linutronix.de>
Wed, 28 Mar 2018 21:01:30 +0000 (23:01 +0200)
commitc28d62cf52d791ba5f6db7ce525ed06b86291c82
tree683f0b9f5b8faa613a46da023b1b7a4bd204c33e
parentac605bee0bfab40fd5d11964705e907d2d5a32de
locking/rtmutex: Handle non enqueued waiters gracefully in remove_waiter()

In -RT task_blocks_on_rt_mutex() may return with -EAGAIN due to
(->pi_blocked_on == PI_WAKEUP_INPROGRESS) before it added itself as a
waiter. In such a case remove_waiter() must not be called because without a
waiter it will trigger the BUG_ON() statement.

This was initially reported by Yimin Deng. Thomas Gleixner fixed it then
with an explicit check for waiters before calling remove_waiter().

Instead of an explicit NULL check before calling rt_mutex_top_waiter() make
the function return NULL if there are no waiters. With that fixed the now
pointless NULL check is removed from rt_mutex_slowlock().

Reported-and-debugged-by: Yimin Deng <yimin11.deng@gmail.com>
Suggested-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Link: https://lkml.kernel.org/r/CAAh1qt=DCL9aUXNxanP5BKtiPp3m+qj4yB+gDohhXPVFCxWwzg@mail.gmail.com
Link: https://lkml.kernel.org/r/20180327121438.sss7hxg3crqy4ecd@linutronix.de
kernel/locking/rtmutex.c
kernel/locking/rtmutex_common.h