From: "Zqiang" <qiang.zhang@linux.dev>
To: paulmck@kernel.org
Cc: frederic@kernel.org, neeraj.upadhyay@kernel.org,
joelagnelf@nvidia.com, urezki@gmail.com, boqun@kernel.org,
rcu@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rcu-tasks: Update comments in call_rcu_tasks_generic()
Date: Thu, 16 Jul 2026 12:09:08 +0000 [thread overview]
Message-ID: <7ac329e8d59e4dfbb8a19d127e1dff6915735872@linux.dev> (raw)
In-Reply-To: <4f9b2c64-3d9d-4b39-af13-9ac726e21660@paulmck-laptop>
>
> On Mon, Jul 13, 2026 at 06:31:26PM +0800, Zqiang wrote:
>
> >
> > Currently, the comments: "We can't create the thread unless interrupts
> > are enabled." from 'commit 4929c913bda5 ("rcu: Make call_rcu_tasks()
> > tolerate first call with irqs disabled")', now the kthread creation
> > has been move to core_initcall() time from 'commit c63eb17ff06d
> > ("rcu: Create call_rcu_tasks() kthread at boot time")', and use the
> > irq_work does deferred wakeup. this commit therefore update comments
> > in call_rcu_tasks_generic().
> >
> > Signed-off-by: Zqiang <qiang.zhang@linux.dev>
> >
> Queued and pushed both, thank you! I adjusted the comment and commit log,
> so please double-check them in case I messed something up.
Thank you for adjusted comment! I have been checked(including previous SRCU patches).
Thanks
Zqiang
>
> Thanx, Paul
>
> >
> > ---
> > kernel/rcu/tasks.h | 6 +++++-
> > 1 file changed, 5 insertions(+), 1 deletion(-)
> >
> > diff --git a/kernel/rcu/tasks.h b/kernel/rcu/tasks.h
> > index a2ca79d1dd6a..089a0d5a5cc9 100644
> > --- a/kernel/rcu/tasks.h
> > +++ b/kernel/rcu/tasks.h
> > @@ -395,7 +395,11 @@ static void call_rcu_tasks_generic(struct rcu_head *rhp, rcu_callback_t func,
> > raw_spin_unlock_irqrestore(&rtp->cbs_gbl_lock, flags);
> > }
> > rcu_read_unlock();
> > - /* We can't create the thread unless interrupts are enabled. */
> > + // We can't create the kthread with interrupts disabled,
> > + // or a spinlock might be held, the kthread creation has
> > + // been move to core_initcall() time.
> > + // at the same time, use the irq_work does deferred wakeup
> > + // to avoid potential lockdep splat.
> > if (needwake && READ_ONCE(rtp->kthread_ptr))
> > irq_work_queue(&rtpcp->rtp_irq_work);
> > }
> > --
> > 2.17.1
> >
>
prev parent reply other threads:[~2026-07-16 12:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 10:31 [PATCH] rcu-tasks: Update comments in call_rcu_tasks_generic() Zqiang
2026-07-14 20:21 ` Paul E. McKenney
2026-07-16 12:09 ` Zqiang [this message]
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=7ac329e8d59e4dfbb8a19d127e1dff6915735872@linux.dev \
--to=qiang.zhang@linux.dev \
--cc=boqun@kernel.org \
--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