diff options
| author | Peter Zijlstra <[email protected]> | 2024-10-08 11:26:06 +0200 |
|---|---|---|
| committer | Thomas Gleixner <[email protected]> | 2024-10-24 23:03:30 +0200 |
| commit | d12b802f183667d4c28589314c99c380a458d57e (patch) | |
| tree | 6ec01d74266a8633b6cb1e46447791bf924cd540 | |
| parent | 77abd3b7d9bf384306872b6201b1dfeb1e899892 (diff) | |
locking/rtmutex: Fix misleading comment
Going through the RCU-boost and rtmutex code, I ran into this utterly
confusing comment. Fix it to avoid confusing future readers.
[ tglx: Wordsmithed the comment ]
Signed-off-by: Peter Zijlstra (Intel) <[email protected]>
Signed-off-by: Thomas Gleixner <[email protected]>
Reviewed-by: Sebastian Andrzej Siewior <[email protected]>
Link: https://lore.kernel.org/all/[email protected]
| -rw-r--r-- | kernel/locking/rtmutex_api.c | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/kernel/locking/rtmutex_api.c b/kernel/locking/rtmutex_api.c index a6974d044593..7e79258feb27 100644 --- a/kernel/locking/rtmutex_api.c +++ b/kernel/locking/rtmutex_api.c @@ -175,10 +175,10 @@ bool __sched __rt_mutex_futex_unlock(struct rt_mutex_base *lock, } /* - * We've already deboosted, mark_wakeup_next_waiter() will - * retain preempt_disabled when we drop the wait_lock, to - * avoid inversion prior to the wakeup. preempt_disable() - * therein pairs with rt_mutex_postunlock(). + * mark_wakeup_next_waiter() deboosts and retains preemption + * disabled when dropping the wait_lock, to avoid inversion prior + * to the wakeup. preempt_disable() therein pairs with the + * preempt_enable() in rt_mutex_postunlock(). */ mark_wakeup_next_waiter(wqh, lock); |