aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/tools/perf/util/scripting-engines/trace-event-python.c
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2021-05-23 06:30:08 -1000
committerLinus Torvalds <torvalds@linux-foundation.org>2021-05-23 06:30:08 -1000
commit0898678c742ee913691d7f4a1606309825eee33b (patch)
tree295cbe24bea6550d208dee4862d32d1354b9cc97 /tools/perf/util/scripting-engines/trace-event-python.c
parentMerge tag 'irq-urgent-2021-05-23' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip (diff)
parentlocking/mutex: clear MUTEX_FLAGS if wait_list is empty due to signal (diff)
downloadwireguard-linux-0898678c742ee913691d7f4a1606309825eee33b.tar.xz
wireguard-linux-0898678c742ee913691d7f4a1606309825eee33b.zip
Merge tag 'locking-urgent-2021-05-23' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
Pull locking fixes from Thomas Gleixner: "Two locking fixes: - Invoke the lockdep tracepoints in the correct place so the ordering is correct again - Don't leave the mutex WAITER bit stale when the last waiter is dropping out early due to a signal as that forces all subsequent lock operations needlessly into the slowpath until it's cleaned up again" * tag 'locking-urgent-2021-05-23' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: locking/mutex: clear MUTEX_FLAGS if wait_list is empty due to signal locking/lockdep: Correct calling tracepoints
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions