diff options
author | Thomas Gleixner <tglx@linutronix.de> | 2021-01-20 16:00:24 +0100 |
---|---|---|
committer | Thomas Gleixner <tglx@linutronix.de> | 2021-01-26 15:10:58 +0100 |
commit | 12bb3f7f1b03d5913b3f9d4236a488aa7774dfe9 (patch) | |
tree | 0eb8ee3e490e16e316d22cab5ce09e16ff0176c8 /net/switchdev/switchdev.c | |
parent | 13391c60da3308ed9980de0168f74cce6c62ac1d (diff) | |
download | linux-12bb3f7f1b03d5913b3f9d4236a488aa7774dfe9.tar.gz linux-12bb3f7f1b03d5913b3f9d4236a488aa7774dfe9.tar.bz2 linux-12bb3f7f1b03d5913b3f9d4236a488aa7774dfe9.zip |
futex: Ensure the correct return value from futex_lock_pi()
In case that futex_lock_pi() was aborted by a signal or a timeout and the
task returned without acquiring the rtmutex, but is the designated owner of
the futex due to a concurrent futex_unlock_pi() fixup_owner() is invoked to
establish consistent state. In that case it invokes fixup_pi_state_owner()
which in turn tries to acquire the rtmutex again. If that succeeds then it
does not propagate this success to fixup_owner() and futex_lock_pi()
returns -EINTR or -ETIMEOUT despite having the futex locked.
Return success from fixup_pi_state_owner() in all cases where the current
task owns the rtmutex and therefore the futex and propagate it correctly
through fixup_owner(). Fixup the other callsite which does not expect a
positive return value.
Fixes: c1e2f0eaf015 ("futex: Avoid violating the 10th rule of futex")
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Cc: stable@vger.kernel.org
Diffstat (limited to 'net/switchdev/switchdev.c')
0 files changed, 0 insertions, 0 deletions