You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This reverts commit 5ae263a6ca027c4b79c4dfacfcf4eca8209eefd0, because
disambiguating the per-thread lock is not as useless as it seemed at
first.
Fixes this regression when CONFIG_DEBUG_HARD_SPINLOCKS is on:
[ 52.090120]
[ 52.090129] ============================================
[ 52.090134] WARNING: possible recursive locking detected
[ 52.090139] 5.10.199-00830-g18654c202dd6 torvalds#118 Not tainted
[ 52.090143] --------------------------------------------
[ 52.090147] monitor-dlk-A:4/493 is trying to acquire lock:
[ 52.090152] c34a7010 (__RAWLOCK(&thread->lock)){-.-.}-{0:0}, at: evl_lock_mutex_timeout+0x4e0/0x870
[ 52.090169]
[ 52.090173] but task is already holding lock:
[ 52.090176] c34a5810 (__RAWLOCK(&thread->lock)){-.-.}-{0:0}, at: evl_lock_mutex_timeout+0x4e0/0x870
[ 52.090192]
[ 52.090195] other info that might help us debug this:
[ 52.090199] Possible unsafe locking scenario:
[ 52.090202]
[ 52.090205] CPU0
[ 52.090208] ----
[ 52.090211] lock(__RAWLOCK(&thread->lock));
[ 52.090221] lock(__RAWLOCK(&thread->lock));
[ 52.090229]
[ 52.090233] *** DEADLOCK ***
[ 52.090235]
[ 52.090239] May be due to missing lock nesting notation
[ 52.090242]
[ 52.090246] 2 locks held by monitor-dlk-A:4/493:
[ 52.090249] #0: c2d030d4 (&mon->mutex){....}-{0:0}, at: evl_lock_mutex_timeout+0x104/0x870
[ 52.090267] #1: c34a5810 (__RAWLOCK(&thread->lock)){-.-.}-{0:0}, at: evl_lock_mutex_timeout+0x4e0/0x870
Signed-off-by: Philippe Gerum <[email protected]>
0 commit comments