diff options
| author | Thomas Gleixner <tglx@linutronix.de> | 2014-06-03 12:27:07 +0000 |
|---|---|---|
| committer | Paul Kocialkowski <contact@paulk.fr> | 2014-07-17 16:50:06 +0200 |
| commit | c6889d981012a586c30acf9fc2c0f5b44d24f093 (patch) | |
| tree | f2ec138946dc23c23311065b3c61aee2ee87e1c1 /arch/mn10300/lib/memmove.S | |
| parent | 48c9b318d2fe0d3f2899e16e08f0972ffbd8c2b5 (diff) | |
| download | kernel_samsung_crespo-c6889d981012a586c30acf9fc2c0f5b44d24f093.zip kernel_samsung_crespo-c6889d981012a586c30acf9fc2c0f5b44d24f093.tar.gz kernel_samsung_crespo-c6889d981012a586c30acf9fc2c0f5b44d24f093.tar.bz2 | |
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.
Change-Id: I4eeb2e139b720f1dd46e43407a96b3d9a19aacd1
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
Diffstat (limited to 'arch/mn10300/lib/memmove.S')
0 files changed, 0 insertions, 0 deletions