kernel_optimize_test/kernel/locking
Chris Wilson a63b03e2d2 mutex: Always clear owner field upon mutex_unlock()
Currently if DEBUG_MUTEXES is enabled, the mutex->owner field is only
cleared iff debug_locks is active. This exposes a race to other users of
the field where the mutex->owner may be still set to a stale value,
potentially upsetting mutex_spin_on_owner() among others.

References: https://bugs.freedesktop.org/show_bug.cgi?id=87955
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Acked-by: Davidlohr Bueso <dave@stgolabs.net>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Link: http://lkml.kernel.org/r/1420540175-30204-1-git-send-email-chris@chris-wilson.co.uk
Signed-off-by: Ingo Molnar <mingo@kernel.org>
2015-01-09 11:20:39 +01:00
..
lglock.c
lockdep_internals.h
lockdep_proc.c
lockdep_states.h
lockdep.c locking/lockdep: Revert qrwlock recusive stuff 2014-10-03 06:09:30 +02:00
locktorture.c locktorture: Cleanup header usage 2014-09-30 00:10:02 -07:00
Makefile
mcs_spinlock.c
mcs_spinlock.h
mutex-debug.c mutex: Always clear owner field upon mutex_unlock() 2015-01-09 11:20:39 +01:00
mutex-debug.h
mutex.c locking/mutex: Don't assume TASK_RUNNING 2014-10-28 10:55:08 +01:00
mutex.h
percpu-rwsem.c
qrwlock.c
rtmutex_common.h
rtmutex-debug.c
rtmutex-debug.h
rtmutex-tester.c
rtmutex.c
rtmutex.h
rwsem-spinlock.c
rwsem-xadd.c locking/rwsem: Avoid double checking before try acquiring write lock 2014-10-03 06:09:29 +02:00
rwsem.c
semaphore.c
spinlock_debug.c
spinlock.c