diff options
| author | Leo Yan <[email protected]> | 2021-05-12 20:09:37 +0800 |
|---|---|---|
| committer | Peter Zijlstra <[email protected]> | 2021-05-18 12:53:50 +0200 |
| commit | 89e70d5c583c55088faa2201d397ee30a15704aa (patch) | |
| tree | ba94f0e7778ed78aeabcd843665d63b8667cffa7 /kernel/locking/mutex-debug.h | |
| parent | d07f6ca923ea0927a1024dfccafc5b53b61cfecc (diff) | |
locking/lockdep: Correct calling tracepoints
The commit eb1f00237aca ("lockdep,trace: Expose tracepoints") reverses
tracepoints for lock_contended() and lock_acquired(), thus the ftrace
log shows the wrong locking sequence that "acquired" event is prior to
"contended" event:
<idle>-0 [001] d.s3 20803.501685: lock_acquire: 0000000008b91ab4 &sg_policy->update_lock
<idle>-0 [001] d.s3 20803.501686: lock_acquired: 0000000008b91ab4 &sg_policy->update_lock
<idle>-0 [001] d.s3 20803.501689: lock_contended: 0000000008b91ab4 &sg_policy->update_lock
<idle>-0 [001] d.s3 20803.501690: lock_release: 0000000008b91ab4 &sg_policy->update_lock
This patch fixes calling tracepoints for lock_contended() and
lock_acquired().
Fixes: eb1f00237aca ("lockdep,trace: Expose tracepoints")
Signed-off-by: Leo Yan <[email protected]>
Signed-off-by: Peter Zijlstra (Intel) <[email protected]>
Link: https://lkml.kernel.org/r/[email protected]
Diffstat (limited to 'kernel/locking/mutex-debug.h')
0 files changed, 0 insertions, 0 deletions