diff options
| author | Peter Zijlstra <peterz@infradead.org> | 2021-11-29 18:46:46 +0100 |
|---|---|---|
| committer | Peter Zijlstra <peterz@infradead.org> | 2021-12-04 10:56:23 +0100 |
| commit | 02ea9fc96fe976e7f7e067f38b12202f126e3f2f (patch) | |
| tree | 4df904db607e5635e6f947b2b34cf5067e6d9885 /fs/char_dev.c | |
| parent | e08f343be00c3fe8f9f6ac58085c81bcdd231fab (diff) | |
locking/rtmutex: Squash self-deadlock check for ww_rt_mutex.
Similar to the issues in commits:
6467822b8cc9 ("locking/rtmutex: Prevent spurious EDEADLK return caused by ww_mutexes")
a055fcc132d4 ("locking/rtmutex: Return success on deadlock for ww_mutex waiters")
ww_rt_mutex_lock() should not return EDEADLK without first going through
the __ww_mutex logic to set the required state. In fact, the chain-walk
can deal with the spurious cycles (per the above commits) this check
warns about and is trying to avoid.
Therefore ignore this test for ww_rt_mutex and simply let things fall
in place.
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Link: https://lore.kernel.org/r/20211129174654.668506-4-bigeasy@linutronix.de
Diffstat (limited to 'fs/char_dev.c')
0 files changed, 0 insertions, 0 deletions