Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Chen Jun <chenjun102@huawei.com>
To:     <linux-kernel@vger.kernel.org>, <akpm@linux-foundation.org>,
        <peterz@infradead.org>
CC:     <xuqiang36@huawei.com>
Subject: [PATCH 1/1] lockdep: make PROVE_RAW_LOCK_NESTING depend on PREEMPT_RT
Date:   Thu, 16 Jun 2022 02:29:11 +0000
Message-ID: <20220616022911.35826-1-chenjun102@huawei.com>
MIME-Version: 1.0
Content-Type: text/plain
Precedence: bulk

CONFIG_PROVE_RAW_LOCK_NESTING is used to check two things.
1. calling spin_lock in hardirq.
2. raw_spinlock - spinlock nesting.
The error messages like below:
[   13.485711] [ BUG: Invalid wait context ]
However there is no problem on non-PREEMPT_RT kernel. The messages may be
confusing and disturbing. 

Therefore, do not check raw_spinlock - spinlock nesting
on non-PREEMPT_RT kernel.

Signed-off-by: Chen Jun <chenjun102@huawei.com>
---
 lib/Kconfig.debug | 1 +
 1 file changed, 1 insertion(+)

diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index bd90664a2783..163d3a6606f3 100644
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -1227,6 +1227,7 @@ config PROVE_LOCKING
 config PROVE_RAW_LOCK_NESTING
 	bool "Enable raw_spinlock - spinlock nesting checks"
 	depends on PROVE_LOCKING
+	depends on PREEMPT_RT
 	default n
 	help
 	 Enable the raw_spinlock vs. spinlock nesting checks which ensure
-- 
2.17.1