[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2f93a746-e23e-4e35-aafc-2ecde8b5f172@linux.dev>
Date: Thu, 25 Sep 2025 09:50:17 +0800
From: luoxuanqiang <xuanqiang.luo@...ux.dev>
To: Jakub Kicinski <kuba@...nel.org>
Cc: edumazet@...gle.com, kuniyu@...gle.com, kerneljasonxing@...il.com,
davem@...emloft.net, netdev@...r.kernel.org,
Xuanqiang Luo <luoxuanqiang@...inos.cn>
Subject: Re: [PATCH net-next v5 1/3] rculist: Add hlist_nulls_replace_rcu()
and hlist_nulls_replace_init_rcu()
在 2025/9/25 08:54, Jakub Kicinski 写道:
> On Wed, 24 Sep 2025 09:50:32 +0800 xuanqiang.luo@...ux.dev wrote:
>> 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")
> You most definitely have to CC RCU maintainers on this patch.
Got it, I'll make sure to CC the RCU maintainers in the next version.
Thanks for the reminder!
Powered by blists - more mailing lists