On Tue, Aug 11, 2026 at 04:54:20PM +0200, Frederic Weisbecker wrote:
> Le Tue, Aug 11, 2026 at 08:29:51AM +0800, Zqiang a écrit :
> > 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 find that the allocation of srcu_node
> > tree has been completed, but the ss_state is still less than SRCU_SIZE_BIG,
> > the mask=~0 causes delay_work timer be queued on every CPU which has
> > been online regardless of whether it's sdp->srcu_cblist has callbacks.
> > the 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 <[email protected]>
> > Reported-by: kernel test robot <[email protected]>
> > Closes: https://lore.kernel.org/oe-lkp/[email protected]/
> > Tested-by: kernel test robot <[email protected]>
> > Signed-off-by: Zqiang <[email protected]>
>
> Reviewed-by: Frederic Weisbecker <[email protected]>
I pulled this in for further review and testing. My plan is to fold
it in to the commit that it fixes, of course with attribution.
Thank you both!
Thanx, Paul
