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 [thread overview]
Message-ID: <20220616022911.35826-1-chenjun102@huawei.com> (raw)
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
reply other threads:[~2022-06-16 2:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220616022911.35826-1-chenjun102@huawei.com \
--to=chenjun102@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=xuqiang36@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox