From: "Zqiang" <qiang.zhang@linux.dev>
To: paulmck@kernel.org
Cc: frederic@kernel.org, neeraj.upadhyay@kernel.org,
joelagnelf@nvidia.com, boqun.feng@gmail.com, urezki@gmail.com,
rcu@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] srcu/tiny: Remove preempt_disable/enable() in srcu_gp_start_if_needed()
Date: Mon, 08 Sep 2025 13:19:44 +0000 [thread overview]
Message-ID: <63d537e65b7f4b6f77a16112a871103d07a248d2@linux.dev> (raw)
In-Reply-To: <9dfa7d4f-6e3f-4084-a14f-beb1db06f817@paulmck-laptop>
>
> On Mon, Sep 08, 2025 at 08:31:55AM +0800, Zqiang wrote:
>
> >
> > Currently, the srcu_gp_start_if_needed() is always be invoked in
> > preempt disable's critical section, this commit therefore remove
> > redundant preempt_disable/enable() in srcu_gp_start_if_needed().
> >
> > Fixes: 65b4a59557f6 ("srcu: Make Tiny SRCU explicitly disable preemption")
> > Signed-off-by: Zqiang <qiang.zhang@linux.dev>
> >
> Looks good, but what would be a good way to make this code defend itself
> against being invoked from someplace else that did have preemption
> enabled? Especially given that the Tree SRCU version of this function
> does get invoked with preemption enabled?
ok, maybe we can add lockdep_assert_preemption_disabled() in
the srcu_gp_start_if_needed() ?
Thanks
Zqiang
>
> Thanx, Paul
>
> >
> > ---
> > kernel/rcu/srcutiny.c | 3 ---
> > 1 file changed, 3 deletions(-)
> >
> > diff --git a/kernel/rcu/srcutiny.c b/kernel/rcu/srcutiny.c
> > index b52ec45698e8..417bd0e4457c 100644
> > --- a/kernel/rcu/srcutiny.c
> > +++ b/kernel/rcu/srcutiny.c
> > @@ -181,10 +181,8 @@ static void srcu_gp_start_if_needed(struct srcu_struct *ssp)
> > {
> > unsigned long cookie;
> >
> > - preempt_disable(); // Needed for PREEMPT_LAZY
> > cookie = get_state_synchronize_srcu(ssp);
> > if (ULONG_CMP_GE(READ_ONCE(ssp->srcu_idx_max), cookie)) {
> > - preempt_enable();
> > return;
> > }
> > WRITE_ONCE(ssp->srcu_idx_max, cookie);
> > @@ -194,7 +192,6 @@ static void srcu_gp_start_if_needed(struct srcu_struct *ssp)
> > else if (list_empty(&ssp->srcu_work.entry))
> > list_add(&ssp->srcu_work.entry, &srcu_boot_list);
> > }
> > - preempt_enable();
> > }
> >
> > /*
> > --
> > 2.48.1
> >
>
next prev parent reply other threads:[~2025-09-08 13:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-08 0:31 [PATCH] srcu/tiny: Remove preempt_disable/enable() in srcu_gp_start_if_needed() Zqiang
2025-09-08 1:29 ` Paul E. McKenney
2025-09-08 13:19 ` Zqiang [this message]
2025-09-09 0:23 ` Paul E. McKenney
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=63d537e65b7f4b6f77a16112a871103d07a248d2@linux.dev \
--to=qiang.zhang@linux.dev \
--cc=boqun.feng@gmail.com \
--cc=frederic@kernel.org \
--cc=joelagnelf@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neeraj.upadhyay@kernel.org \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=urezki@gmail.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;
as well as URLs for NNTP newsgroup(s).