netdev - Re: [PATCH net-next v7 1/3] rculist: Add hlist_nulls_replace_rcu() and hlist_nulls_replace_init

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAL+tcoBy+8RvKXDB2V0mcJ3pOFsrXEsaNYM_o21bk2Q1cLiNSA@mail.gmail.com>
Date: Mon, 13 Oct 2025 14:26:46 +0800
From: Jason Xing <kerneljasonxing@...il.com>
To: Jiayuan Chen <jiayuan.chen@...ux.dev>
Cc: Paolo Abeni <pabeni@...hat.com>, kuba@...nel.org, edumazet@...gle.com, 
	davem@...emloft.net, horms@...nel.org, kuniyu@...gle.com, 
	xuanqiang.luo@...ux.dev, "Paul E. McKenney" <paulmck@...nel.org>, netdev@...r.kernel.org, 
	Xuanqiang Luo <luoxuanqiang@...inos.cn>, Frederic Weisbecker <frederic@...nel.org>, 
	Neeraj Upadhyay <neeraj.upadhyay@...nel.org>
Subject: Re: [PATCH net-next v7 1/3] rculist: Add hlist_nulls_replace_rcu()
 and hlist_nulls_replace_init_rcu()

On Mon, Oct 13, 2025 at 1:36 PM Jiayuan Chen <jiayuan.chen@...ux.dev> wrote:
>
> On Tue, Sep 30, 2025 at 11:16:00AM +0800, Paolo Abeni wrote:
> > On 9/26/25 9:40 AM, xuanqiang.luo@...ux.dev wrote:
> > > From: Xuanqiang Luo <luoxuanqiang@...inos.cn>
> > >
> > > Add two functions to atomically replace RCU-protected hlist_nulls entries.
> [...]
> > >
> > > Signed-off-by: Xuanqiang Luo <luoxuanqiang@...inos.cn>
> >
> > This deserves explicit ack from RCU maintainers.
> >
> > Since we are finalizing the net-next PR, I suggest to defer this series
> > to the next cycle, to avoid rushing such request.
> >
> > Thanks,
> >
> > Paolo
>
> Hi maintainers,
>
> This patch was previously held off due to the merge window.
>
> Now that the merge net-next has open and no further changes are required,
> could we please consider merging it directly?
>
> Apologies for the slight push, but I'm hoping we can get a formal
> commit backported to our production branch.

I suppose a new version that needs to be rebased is necessary.

Thanks,
Jason