summaryrefslogtreecommitdiffstats
path: root/Documentation/SAK.txt
diff options
context:
space:
mode:
authorThomas Gleixner <tglx@linutronix.de>2014-06-03 14:27:07 +0200
committerLinus Torvalds <torvalds@linux-foundation.org>2014-06-05 21:31:07 +0200
commit13fbca4c6ecd96ec1a1cfa2e4f2ce191fe928a5e (patch)
tree8789bcd2b04e6dbceda2377ca67575e5fa618876 /Documentation/SAK.txt
parentfutex: Validate atomic acquisition in futex_lock_pi_atomic() (diff)
downloadlinux-13fbca4c6ecd96ec1a1cfa2e4f2ce191fe928a5e.tar.xz
linux-13fbca4c6ecd96ec1a1cfa2e4f2ce191fe928a5e.zip
futex: Always cleanup owner tid in unlock_pi
If the owner died bit is set at futex_unlock_pi, we currently do not cleanup the user space futex. So the owner TID of the current owner (the unlocker) persists. That's observable inconsistant state, especially when the ownership of the pi state got transferred. Clean it up unconditionally. Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Cc: Kees Cook <keescook@chromium.org> Cc: Will Drewry <wad@chromium.org> Cc: Darren Hart <dvhart@linux.intel.com> Cc: stable@vger.kernel.org Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'Documentation/SAK.txt')
0 files changed, 0 insertions, 0 deletions