diff options
| author | Thomas Gleixner <[email protected]> | 2023-09-08 18:22:53 +0200 |
|---|---|---|
| committer | Peter Zijlstra <[email protected]> | 2023-09-20 09:31:14 +0200 |
| commit | 45f67f30a22f264bc7a0a61255c2ee1a838e9403 (patch) | |
| tree | cea2fb874c26c17d8f75c5957ce2cdaadce24e69 /tools/perf/scripts/python/bin/stackcollapse-record | |
| parent | d14f9e930b9073de264c106bf04968286ef9b3a4 (diff) | |
locking/rtmutex: Add a lockdep assert to catch potential nested blocking
There used to be a BUG_ON(current->pi_blocked_on) in the lock acquisition
functions, but that vanished in one of the rtmutex overhauls.
Bring it back in form of a lockdep assert to catch code paths which take
rtmutex based locks with current::pi_blocked_on != NULL.
Reported-by: Crystal Wood <[email protected]>
Signed-off-by: Thomas Gleixner <[email protected]>
Signed-off-by: "Peter Zijlstra (Intel)" <[email protected]>
Signed-off-by: Sebastian Andrzej Siewior <[email protected]>
Signed-off-by: Peter Zijlstra (Intel) <[email protected]>
Link: https://lkml.kernel.org/r/[email protected]
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions