From: luoxuanqiang <xuanqiang.luo@linux.dev>
To: Paolo Abeni <pabeni@redhat.com>,
edumazet@google.com, kuniyu@google.com,
"Paul E. McKenney" <paulmck@kernel.org>
Cc: kerneljasonxing@gmail.com, davem@davemloft.net, kuba@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: Wed, 1 Oct 2025 23:03:39 +0800 [thread overview]
Message-ID: <d11a4e1c-b44c-4076-8de8-326183ebc3d1@linux.dev> (raw)
In-Reply-To: <f64b89b1-d01c-41d6-9158-e7c14d236d2d@redhat.com>
在 2025/9/30 17:16, Paolo Abeni 写道:
> 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.
>>
>> Keep using WRITE_ONCE() to assign values to ->next and ->pprev, as
>> mentioned in the patch below:
>> commit efd04f8a8b45 ("rcu: Use WRITE_ONCE() for assignments to ->next for
>> rculist_nulls")
>> commit 860c8802ace1 ("rcu: Use WRITE_ONCE() for assignments to ->pprev for
>> hlist_nulls")
>>
>> 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
>
No problem. Thanks for noticing this series of patches!
I'll resend them in the next cycle if they get forgotten.
Thanks!
Xuanqiang
next prev parent reply other threads:[~2025-10-01 15:03 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 [this message]
2025-10-13 5:36 ` Jiayuan Chen
2025-10-13 6:26 ` Jason Xing
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=d11a4e1c-b44c-4076-8de8-326183ebc3d1@linux.dev \
--to=xuanqiang.luo@linux.dev \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=frederic@kernel.org \
--cc=kerneljasonxing@gmail.com \
--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 \
/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).