From: luoxuanqiang <xuanqiang.luo@linux•dev>
To: Simon Horman <horms@kernel•org>
Cc: Jason Xing <kerneljasonxing@gmail•com>,
Jiayuan Chen <jiayuan.chen@linux•dev>,
Paolo Abeni <pabeni@redhat•com>,
kuba@kernel•org, edumazet@google•com, davem@davemloft•net,
kuniyu@google•com, "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: Tue, 14 Oct 2025 10:29:11 +0800 [thread overview]
Message-ID: <d644c8af-2ffe-41c1-bc6d-3f95ddbac756@linux.dev> (raw)
In-Reply-To: <aOzrup9K8AE_dV28@horms.kernel.org>
在 2025/10/13 20:08, Simon Horman 写道:
> On Mon, Oct 13, 2025 at 03:04:34PM +0800, luoxuanqiang wrote:
>> 在 2025/10/13 14:26, Jason Xing 写道:
>>> 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
>> I’ve rebased the series of patches onto the latest codebase locally and
>> didn’t encounter any errors.
>>
>> If there’s anything else I can do to help get these patches merged, just
>> let me know.
> Hi,
>
> The patch-set has been marked as "Deffered" in Patchwork.
> Presumably by Paolo in conjunction with his response above.
> As such the patch-set needs to be (rebased and) reposted in
> order for it to be considered by the maintainers again.
>
> I think the best practice is for this to happen _after_ one
> of the maintainers has sent an "ANN" email announcing that
> net-next has re-opened. I don't believe that has happened yet.
>
> Thanks!
Dear Simon,
Thanks for the detailed explanation. I think we now know how
to handle this kind of situation.
net‑next has been reopened, and I have rebased and resent
the patch-set.
Thanks!
next prev parent reply other threads:[~2025-10-14 2:29 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
2025-10-13 7:04 ` luoxuanqiang
2025-10-13 12:08 ` Simon Horman
2025-10-14 2:29 ` luoxuanqiang [this message]
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=d644c8af-2ffe-41c1-bc6d-3f95ddbac756@linux.dev \
--to=xuanqiang.luo@linux$(echo .)dev \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=frederic@kernel$(echo .)org \
--cc=horms@kernel$(echo .)org \
--cc=jiayuan.chen@linux$(echo .)dev \
--cc=kerneljasonxing@gmail$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=kuniyu@google$(echo .)com \
--cc=luoxuanqiang@kylinos$(echo .)cn \
--cc=neeraj.upadhyay@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=paulmck@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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