LVS
lvs-devel
Google
 
Web LinuxVirtualServer.org

Re: [PATCHv6 net-next 01/14] rculist_bl: add hlist_bl_for_each_entry_con

To: Florian Westphal <fw@xxxxxxxxx>
Subject: Re: [PATCHv6 net-next 01/14] rculist_bl: add hlist_bl_for_each_entry_continue_rcu
Cc: Simon Horman <horms@xxxxxxxxxxxx>, lvs-devel@xxxxxxxxxxxxxxx, netfilter-devel@xxxxxxxxxxxxxxx, Dust Li <dust.li@xxxxxxxxxxxxxxxxx>, Jiejian Wu <jiejian@xxxxxxxxxxxxxxxxx>, rcu@xxxxxxxxxxxxxxx
From: Julian Anastasov <ja@xxxxxx>
Date: Thu, 23 Oct 2025 16:33:45 +0300 (EEST)
        Hello,

On Thu, 23 Oct 2025, Florian Westphal wrote:

> Julian Anastasov <ja@xxxxxx> wrote:
> > Change the old hlist_bl_first_rcu to hlist_bl_first_rcu_dereference
> > to indicate that it is a RCU dereference.
> > 
> > Add hlist_bl_next_rcu and hlist_bl_first_rcu to use RCU pointers
> > and use them to fix sparse warnings.
> > 
> > Add hlist_bl_for_each_entry_continue_rcu.
> > 
> > Signed-off-by: Julian Anastasov <ja@xxxxxx>
> > ---
> >  include/linux/rculist_bl.h | 49 +++++++++++++++++++++++++++++++-------
> >  1 file changed, 40 insertions(+), 9 deletions(-)
> 
> Are the RCU maintainers OK with this?
> An explicit Ack or RvB would be good to have.

        Paul McKenney requested on 15 Aug 2023 some changes
for 1st version:

https://archive.linuxvirtualserver.org/html/lvs-devel/2023-08/msg00044.html

        And they are now present in v2+:

https://archive.linuxvirtualserver.org/html/lvs-devel/2023-08/msg00057.html

        So, the RCU change is expected to be ack-ed after
the other patches are accepted. I'm also expecting review and
ack from Simon, so that we can finally include the patchset
to -next...

Regards

--
Julian Anastasov <ja@xxxxxx>



<Prev in Thread] Current Thread [Next in Thread>