The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Zqiang" <qiang.zhang@linux.dev>
To: "Breno Leitao" <leitao@debian.org>
Cc: paulmck@kernel.org, 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 v2] srcu: Fix WARN_ON() for timer_delete_sync() in cleanup_srcu_struct()
Date: Mon, 10 Aug 2026 23:31:48 +0000	[thread overview]
Message-ID: <3e8f3aa2badb3eb667c43443f642e9b17aa0a484@linux.dev> (raw)
In-Reply-To: <annZejMO4k33rdn9@gmail.com>

> 
> On Mon, Aug 10, 2026 at 06:55:22PM +0800, Zqiang wrote:
> 
> > 
> > The WARN_ON() for timer_delete_sync() means that the caller forgot to
> >  call srcu_barrier() before cleanup. however, it still can trigger even
> >  when srcu_barrier() was properly called.
> >  
> >  When a SRCU grace period ends and ss_state < SRCU_SIZE_BIG, the mask=~0
> >  causes delay_work timer be queued on every online CPU regardless of
> >  whether it's sdp->srcu_cblist has callbacks. srcu_barrier() only wait
> >  srcu_barrier_head's callbacks to complete, however, the srcu_barrier_head
> >  will not be inserted into an empty sdp->srcu_cblist. after that, when
> >  cleanup_srcu_struct() finds a pending delay_work timer on a CPU with no
> >  callbacks, triggering a false positive.
> >  
> >  This commit therefore add rcu_segcblist_n_cbs() to WARN_ON(), make the
> >  warning triggers only when the timer is still pending and there are actual
> >  outstanding callbacks.
> >  
> >  Fixes: 05c3e88488ed ("srcu: Queue sdp->work when the delay timer is successfully deleted")
> >  Reported-by: Breno Leitao <leitao@debian.org>
> >  Reported-by: kernel test robot <oliver.sang@intel.com> 
> >  Closes: https://lore.kernel.org/oe-lkp/202608060833.bce92909-lkp@intel.com/ 
> >  Tested-by: kernel test robot <oliver.sang@intel.com>
> >  Signed-off-by: Zqiang <qiang.zhang@linux.dev>
> >  ---
> >  kernel/rcu/srcutree.c | 5 +++--
> >  1 file changed, 3 insertions(+), 2 deletions(-)
> >  
> >  diff --git a/kernel/rcu/srcutree.c b/kernel/rcu/srcutree.c
> >  index 35fface51d50..090dddfc7463 100644
> >  --- a/kernel/rcu/srcutree.c
> >  +++ b/kernel/rcu/srcutree.c
> >  @@ -753,8 +753,9 @@ void cleanup_srcu_struct(struct srcu_struct *ssp)
> >  
> >  // Call srcu_barrier() before this cleanup_srcu_struct()
> >  // to avoid triggering this WARN_ON().
> >  - if (WARN_ON(timer_delete_sync(&sdp->delay_work)) &&
> >  - rcu_cpu_beenfullyonline(sdp->cpu))
> >  + if (WARN_ON(timer_delete_sync(&sdp->delay_work) &&
> >  + rcu_segcblist_n_cbs(&sdp->srcu_cblist)) &&
> >  + rcu_cpu_beenfullyonline(sdp->cpu))
> > 
> This is quite hard to read, mainly with this indentation.
> 
> You probably want to rewrite the checks , otherwise the indentation
> should be something like, which is horrible (although correct?):
> 
>  if (WARN_ON(timer_delete_sync(&sdp->delay_work) &&
>  rcu_segcblist_n_cbs(&sdp->srcu_cblist)) &&
>  rcu_cpu_beenfullyonline(sdp->cpu))

Will update and resend (I still mark v2 because v1 has not been sent before).

Thanks
Zqiang

> 
> Would something like this work?
> 
>  if (rcu_cpu_beenfullyonline(sdp->cpu) &&
>  WARN_ON(timer_delete_sync(&sdp->delay_work) &&
>  rcu_segcblist_n_cbs(&sdp->srcu_cblist)))
>

  reply	other threads:[~2026-08-10 23:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-10 10:55 [PATCH v2] srcu: Fix WARN_ON() for timer_delete_sync() in cleanup_srcu_struct() Zqiang
2026-08-10 14:04 ` Breno Leitao
2026-08-10 23:31   ` Zqiang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-08-11  0:29 Zqiang

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=3e8f3aa2badb3eb667c43443f642e9b17aa0a484@linux.dev \
    --to=qiang.zhang@linux.dev \
    --cc=boqun@kernel.org \
    --cc=frederic@kernel.org \
    --cc=joelagnelf@nvidia.com \
    --cc=leitao@debian.org \
    --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