UPSTREAM: futex: Fix incorrect should_fail_futex() handling
[ Upstream commit 921c7ebd1337d1a46783d7e15a850e12aed2eaa0 ] If should_futex_fail() returns true in futex_wake_pi(), then the 'ret' variable is set to -EFAULT and then immediately overwritten. So the failure injection is non-functional. Fix it by actually leaving the function and returning -EFAULT. The Fixes tag is kinda blury because the initial commit which introduced failure injection was already sloppy, but the below mentioned commit broke it completely. [ tglx: Massaged changelog ] Fixes: 6b4f4bc9 ("locking/futex: Allow low-level atomic operations to return -EAGAIN") Signed-off-by:Mateusz Nosek <mateusznosek0@gmail.com> Signed-off-by:
Thomas Gleixner <tglx@linutronix.de> Link: https://lore.kernel.org/r/20200927000858.24219-1-mateusznosek0@gmail.com Signed-off-by:
Sasha Levin <sashal@kernel.org> (cherry picked from commit 2db75903) Signed-off-by:
Greg Kroah-Hartman <gregkh@google.com> Change-Id: I22198b7a65630cb5649f3e889810783b147bfada
Loading
Please register or sign in to comment