diff options
author | Thomas Gleixner <[email protected]> | 2016-11-30 21:04:45 +0000 |
---|---|---|
committer | Ingo Molnar <[email protected]> | 2016-12-02 11:13:57 +0100 |
commit | 84d82ec5b9046ecdf16031d3e93a66ef50257402 (patch) | |
tree | 716c8ca677edf6cc92677f7a647cdd9bfa641af9 /tools/perf/scripts/python/bin/export-to-postgresql-report | |
parent | b5016e8203003c44264ec88fe2276ff54a51f689 (diff) |
locking/rtmutex: Explain locking rules for rt_mutex_proxy_unlock()/init_proxy_locked()
While debugging the unlock vs. dequeue race which resulted in state
corruption of futexes the lockless nature of rt_mutex_proxy_unlock()
caused some confusion.
Add commentry to explain why it is safe to do this lockless. Add matching
comments to rt_mutex_init_proxy_locked() for completeness sake.
Signed-off-by: Thomas Gleixner <[email protected]>
Acked-by: Peter Zijlstra (Intel) <[email protected]>
Cc: David Daney <[email protected]>
Cc: Linus Torvalds <[email protected]>
Cc: Mark Rutland <[email protected]>
Cc: Peter Zijlstra <[email protected]>
Cc: Sebastian Siewior <[email protected]>
Cc: Steven Rostedt <[email protected]>
Cc: Will Deacon <[email protected]>
Link: http://lkml.kernel.org/r/[email protected]
Signed-off-by: Ingo Molnar <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin/export-to-postgresql-report')
0 files changed, 0 insertions, 0 deletions