From: Waiman Long <llong@redhat.com>
To: Hillf Danton <hdanton@sina.com>, Waiman Long <llong@redhat.com>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
pengdonglin <dolinux.peng@gmail.com>,
linux-kernel@vger.kernel.org,
"Paul E . McKenney" <paulmck@kernel.org>
Subject: Re: [PATCH] rcu: Remove redundant rcu_read_lock/unlock() in spin_lock critical sections
Date: Sat, 13 Sep 2025 13:23:03 -0400 [thread overview]
Message-ID: <10adb9b7-ea19-407b-818e-79061a067e13@redhat.com> (raw)
In-Reply-To: <20250913080018.7032-1-hdanton@sina.com>
On 9/13/25 4:00 AM, Hillf Danton wrote:
> On Fri, 12 Sep 2025 20:33:31 -0400 Waiman Long wrote:
>> On 9/12/25 5:35 PM, Sebastian Andrzej Siewior wrote:
>>> On 2025-09-12 17:13:09 [-0400], Waiman Long wrote:
>>>> On 9/12/25 2:50 AM, pengdonglin wrote:
>>>>> From: pengdonglin <pengdonglin@xiaomi.com>
>>>>>
>>>>> When CONFIG_PREEMPT_RT is disabled, spin_lock*() operations
>>>>> implicitly
>>>>> disable preemption, which provides RCU read-side protection. When
>>>>> CONFIG_PREEMPT_RT is enabled, spin_lock*() implementations internally
>>>>> manage RCU read-side critical sections.
>>>> I have some doubt about your claim that disabling preemption
>>>> provides RCU
>>>> read-side protection. It is true for some flavors but probably not
>>>> all. I do
>>>> know that disabling interrupt will provide RCU read-side
>>>> protection. So for
>>>> spin_lock_irq*() calls, that is valid. I am not sure about
>>>> spin_lock_bh(),
>>>> maybe it applies there too. we need some RCU people to confirm.
>>> The claim is valid since Paul merged the three flavours we had. Before
>>> that preempt_disable() (and disabling irqs) would match
>>> rcu_read_lock_sched(). rcu_read_lock() and rcu_read_lock_bh() were
>>> different in terms of grace period and clean up.
>>> So _now_ we could remove it if it makes things easier.
>>
>> Thanks for the clarification.
>>
>> In this case, I think the patch description should mention the commit
>> that unify the 3 RCU flavors to make sure that this patch won't be
>> accidentally backport'ed to an older kernel without the necessary
>> prerequisite commit(s).
>
> This change also affects the dereference helpers.
>
> #define rcu_dereference_check(p, c) \
> __rcu_dereference_check((p), __UNIQUE_ID(rcu), \
> (c) || rcu_read_lock_held(), __rcu)
>
Right, this macro will need to be updated as well to avoid false
positive if we decide that preempt_disabled region is a valid
rcu_read_lock critical section.
Cheers,
Longman
next prev parent reply other threads:[~2025-09-13 17:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-12 6:50 pengdonglin
2025-09-12 21:13 ` Waiman Long
2025-09-12 21:35 ` Sebastian Andrzej Siewior
2025-09-13 0:33 ` Waiman Long
2025-09-13 8:00 ` Hillf Danton
2025-09-13 17:23 ` Waiman Long [this message]
2025-09-13 22:05 ` Paul E. McKenney
2025-09-15 1:29 ` Donglin Peng
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=10adb9b7-ea19-407b-818e-79061a067e13@redhat.com \
--to=llong@redhat.com \
--cc=bigeasy@linutronix.de \
--cc=dolinux.peng@gmail.com \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@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®