aboutsummaryrefslogtreecommitdiff
path: root/kernel/locking/rtmutex-debug.h
diff options
context:
space:
mode:
authorWaiman Long <longman@redhat.com>2021-03-18 13:28:11 -0400
committerIngo Molnar <mingo@kernel.org>2021-03-19 12:13:09 +0100
commit2ea55bbba23e9d36996299664d618393c8602646 (patch)
treefb0fbeefffcfe8eda7c27e77fa5bc2d91d77030f /kernel/locking/rtmutex-debug.h
parent01438749e36bfe53ea25c91568019be775a9782e (diff)
downloadlinux-2ea55bbba23e9d36996299664d618393c8602646.tar.gz
linux-2ea55bbba23e9d36996299664d618393c8602646.tar.bz2
linux-2ea55bbba23e9d36996299664d618393c8602646.zip
locking/locktorture: Fix false positive circular locking splat in ww_mutex test
In order to avoid false positive circular locking lockdep splat when runnng the ww_mutex torture test, we need to make sure that the ww_mutexes have the same lock class as the acquire_ctx. This means the ww_mutexes must have the same lockdep key as the acquire_ctx. Unfortunately the current DEFINE_WW_MUTEX() macro fails to do that. As a result, we add an init method for the ww_mutex test to do explicit ww_mutex_init()'s of the ww_mutexes to avoid the false positive warning. Suggested-by: Peter Zijlstra <peterz@infradead.org> Signed-off-by: Waiman Long <longman@redhat.com> Signed-off-by: Ingo Molnar <mingo@kernel.org> Link: https://lore.kernel.org/r/20210318172814.4400-3-longman@redhat.com
Diffstat (limited to 'kernel/locking/rtmutex-debug.h')
0 files changed, 0 insertions, 0 deletions