aboutsummaryrefslogtreecommitdiffstats
path: root/samples
diff options
context:
space:
mode:
authorThomas Gleixner <tglx@linutronix.de>2014-06-03 12:27:07 +0000
committerPaul Kocialkowski <contact@paulk.fr>2014-07-17 16:51:38 +0200
commit1cdce9c38e971b62d89824196b57cff4e11b4f7a (patch)
tree379a8f776b31bc61a7a3cc6a225cb7b7cd3c0565 /samples
parent8395f2ec35b7a744c8156e5b201e7cc6cb2da18a (diff)
downloadkernel_samsung_aries-1cdce9c38e971b62d89824196b57cff4e11b4f7a.zip
kernel_samsung_aries-1cdce9c38e971b62d89824196b57cff4e11b4f7a.tar.gz
kernel_samsung_aries-1cdce9c38e971b62d89824196b57cff4e11b4f7a.tar.bz2
futex: Always cleanup owner tid in unlock_pi
commit 13fbca4c6ecd96ec1a1cfa2e4f2ce191fe928a5e upstream. 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> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> [steven@steven676.net: make apply to 3.0]
Diffstat (limited to 'samples')
0 files changed, 0 insertions, 0 deletions