From: Jason Xing <kerneljasonxing@gmail.com>
To: Jiayuan Chen <jiayuan.chen@linux.dev>
Cc: Paolo Abeni <pabeni@redhat.com>,
kuba@kernel.org, edumazet@google.com, davem@davemloft.net,
horms@kernel.org, kuniyu@google.com, xuanqiang.luo@linux.dev,
"Paul E. McKenney" <paulmck@kernel.org>,
netdev@vger.kernel.org, Xuanqiang Luo <luoxuanqiang@kylinos.cn>,
Frederic Weisbecker <frederic@kernel.org>,
Neeraj Upadhyay <neeraj.upadhyay@kernel.org>
Subject: Re: [PATCH net-next v7 1/3] rculist: Add hlist_nulls_replace_rcu() and hlist_nulls_replace_init_rcu()
Date: Mon, 13 Oct 2025 14:26:46 +0800 [thread overview]
Message-ID: <CAL+tcoBy+8RvKXDB2V0mcJ3pOFsrXEsaNYM_o21bk2Q1cLiNSA@mail.gmail.com> (raw)
In-Reply-To: <zus4r4dgghmcyyj2bcjiprad4w666u4paqo3c5jgamr5apceje@zzdlbm75h5m5>
On Mon, Oct 13, 2025 at 1:36 PM Jiayuan Chen <jiayuan.chen@linux.dev> wrote:
>
> On Tue, Sep 30, 2025 at 11:16:00AM +0800, Paolo Abeni wrote:
> > On 9/26/25 9:40 AM, xuanqiang.luo@linux.dev wrote:
> > > From: Xuanqiang Luo <luoxuanqiang@kylinos.cn>
> > >
> > > Add two functions to atomically replace RCU-protected hlist_nulls entries.
> [...]
> > >
> > > Signed-off-by: Xuanqiang Luo <luoxuanqiang@kylinos.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
next prev parent reply other threads:[~2025-10-13 6:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-26 7:40 [PATCH net-next v7 0/3] net: Avoid ehash lookup races xuanqiang.luo
2025-09-26 7:40 ` [PATCH net-next v7 1/3] rculist: Add hlist_nulls_replace_rcu() and hlist_nulls_replace_init_rcu() xuanqiang.luo
2025-09-27 20:31 ` Kuniyuki Iwashima
2025-09-30 9:16 ` Paolo Abeni
2025-10-01 15:03 ` luoxuanqiang
2025-10-13 5:36 ` Jiayuan Chen
2025-10-13 6:26 ` Jason Xing [this message]
2025-10-13 7:04 ` luoxuanqiang
2025-10-13 12:08 ` Simon Horman
2025-10-14 2:29 ` luoxuanqiang
2025-10-01 12:19 ` Frederic Weisbecker
2025-10-13 7:31 ` Eric Dumazet
2025-10-13 8:25 ` luoxuanqiang
2025-10-13 9:49 ` Eric Dumazet
2025-10-14 7:20 ` luoxuanqiang
2025-10-14 7:34 ` Eric Dumazet
2025-10-14 8:04 ` luoxuanqiang
2025-10-14 8:09 ` Eric Dumazet
2025-10-14 8:40 ` luoxuanqiang
2025-10-14 10:02 ` Eric Dumazet
2025-10-14 11:40 ` luoxuanqiang
2025-09-26 7:40 ` [PATCH net-next v7 2/3] inet: Avoid ehash lookup race in inet_ehash_insert() xuanqiang.luo
2025-09-26 7:40 ` [PATCH net-next v7 3/3] inet: Avoid ehash lookup race in inet_twsk_hashdance_schedule() xuanqiang.luo
2025-09-27 2:56 ` [PATCH net-next v7 0/3] net: Avoid ehash lookup races Jiayuan Chen
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=CAL+tcoBy+8RvKXDB2V0mcJ3pOFsrXEsaNYM_o21bk2Q1cLiNSA@mail.gmail.com \
--to=kerneljasonxing@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=frederic@kernel.org \
--cc=horms@kernel.org \
--cc=jiayuan.chen@linux.dev \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=luoxuanqiang@kylinos.cn \
--cc=neeraj.upadhyay@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=paulmck@kernel.org \
--cc=xuanqiang.luo@linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).