From: Ryo Takakura <ryotkkr98@gmail.com>
To: boqun.feng@gmail.com
Cc: bigeasy@linutronix.de, clrkwllms@kernel.org,
linux-kernel@vger.kernel.org, linux-rt-devel@lists.linux.dev,
longman@redhat.com, mingo@redhat.com, peterz@infradead.org,
rostedt@goodmis.org, tglx@linutronix.de, will@kernel.org
Subject: Re: [PATCH] lockdep: Fix wait context check on softirq for PREEMPT_RT
Date: Sat, 21 Dec 2024 01:10:16 +0900 [thread overview]
Message-ID: <20241220161016.422991-1-ryotkkr98@gmail.com> (raw)
In-Reply-To: <Z2Sdv6tSEoxiYW4e@boqun-archlinux>
On Thu, 19 Dec 2024 14:27:11 -0800, Boqun Feng wrote:
>The following is the rough idea:
>
>Regards,
>Boqun
>
>----->8
>diff --git a/include/linux/bottom_half.h b/include/linux/bottom_half.h
>index fc53e0ad56d9..7191a753e983 100644
>--- a/include/linux/bottom_half.h
>+++ b/include/linux/bottom_half.h
>@@ -4,6 +4,7 @@
>
> #include <linux/instruction_pointer.h>
> #include <linux/preempt.h>
>+#include <linux/lockdep.h>
>
> #if defined(CONFIG_PREEMPT_RT) || defined(CONFIG_TRACE_IRQFLAGS)
> extern void __local_bh_disable_ip(unsigned long ip, unsigned int cnt);
>@@ -15,9 +16,12 @@ static __always_inline void __local_bh_disable_ip(unsigned long ip, unsigned int
> }
> #endif
>
>+extern struct lockdep_map bh_lock_map;
>+
> static inline void local_bh_disable(void)
> {
> __local_bh_disable_ip(_THIS_IP_, SOFTIRQ_DISABLE_OFFSET);
>+ lock_map_acquire_read(&bh_lock_map);
> }
>
> extern void _local_bh_enable(void);
>@@ -25,11 +29,13 @@ extern void __local_bh_enable_ip(unsigned long ip, unsigned int cnt);
>
> static inline void local_bh_enable_ip(unsigned long ip)
> {
>+ lock_map_release(&bh_lock_map);
> __local_bh_enable_ip(ip, SOFTIRQ_DISABLE_OFFSET);
> }
>
> static inline void local_bh_enable(void)
> {
>+ lock_map_release(&bh_lock_map);
> __local_bh_enable_ip(_THIS_IP_, SOFTIRQ_DISABLE_OFFSET);
> }
>
>diff --git a/kernel/softirq.c b/kernel/softirq.c
>index 8b41bd13cc3d..17d9bf6e0caf 100644
>--- a/kernel/softirq.c
>+++ b/kernel/softirq.c
>@@ -1066,3 +1066,13 @@ unsigned int __weak arch_dynirq_lower_bound(unsigned int from)
> {
> return from;
> }
>+
>+static struct lock_class_key bh_lock_key;
>+struct lockdep_map bh_lock_map = {
>+ .name = "local_bh",
>+ .key = &bh_lock_key,
>+ .wait_type_outer = LD_WAIT_FREE,
>+ .wait_type_inner = LD_WAIT_CONFIG, /* PREEMPT_RT makes BH preemptible. */
>+ .lock_type = LD_LOCK_PERCPU,
>+};
>+EXPORT_SYMBOL_GPL(bh_lock_map);
Self-tests are now all passing. Thanks!
It looks good to me.
Sincerely,
Ryo Takakura
next prev parent reply other threads:[~2024-12-20 16:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 1:20 Ryo Takakura
2024-12-02 10:32 ` Peter Zijlstra
2024-12-03 7:49 ` Boqun Feng
2024-12-03 11:57 ` Ryo Takakura
2024-12-09 16:09 ` Ryo Takakura
2024-12-19 22:27 ` Boqun Feng
2024-12-20 7:15 ` Sebastian Andrzej Siewior
2024-12-20 16:10 ` Ryo Takakura [this message]
2024-12-20 19:00 ` Boqun Feng
2024-12-21 5:17 ` Ryo Takakura
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=20241220161016.422991-1-ryotkkr98@gmail.com \
--to=ryotkkr98@gmail.com \
--cc=bigeasy@linutronix.de \
--cc=boqun.feng@gmail.com \
--cc=clrkwllms@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
/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
all inboxes | Powered by JetHome®