netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: luoxuanqiang <xuanqiang.luo@linux.dev>
To: Kuniyuki Iwashima <kuniyu@google.com>
Cc: edumazet@google.com, "Paul E. McKenney" <paulmck@kernel.org>,
	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 v6 1/3] rculist: Add hlist_nulls_replace_rcu() and hlist_nulls_replace_init_rcu()
Date: Fri, 26 Sep 2025 12:33:19 +0800	[thread overview]
Message-ID: <15ce9ffb-fdd0-4dba-8cfa-b24de99368fb@linux.dev> (raw)
In-Reply-To: <CAAVpQUAi2TLyODdvK=EAh0OyL_ZzLQWA_XrrQaspXTNdEmapWA@mail.gmail.com>


在 2025/9/26 12:02, Kuniyuki Iwashima 写道:
> On Thu, Sep 25, 2025 at 8:23 PM luoxuanqiang <xuanqiang.luo@linux.dev> wrote:
> [...]
>>>> +{
>>>> +       struct hlist_nulls_node *next = old->next;
>>>> +
>>>> +       WRITE_ONCE(new->next, next);
>>>> +       WRITE_ONCE(new->pprev, old->pprev);
>>>> +       rcu_assign_pointer(*(struct hlist_nulls_node __rcu **)new->pprev, new);
>>> nit: define hlist_nulls_prev_rcu() like hlist_nulls_next_rcu().
>> I'm wondering if defining a macro called hlist_nulls_prev_rcu() might
>> be controversial, since it should actually be getting the prev->next
>> rather than the prev itself.
> See hlist_add_before_rcu() for an example:
>
>      rcu_assign_pointer(hlist_pprev_rcu(n), n);
>
> You can define hlist_nulls_pprev_rcu() and use it alike.
>
>      rcu_assign_pointer(hlist_nulls_pprev_rcu(new), new);
>
>
> [...]
>> However, I noticed that in the definition of hlist_pprev_rcu(), it directly
>> uses pprev:
>>
>> #define hlist_pprev_rcu(node)    (*((struct hlist_node __rcu **)((node)->pprev)))
> Note it dereferences *((node)->pprev).  The macro is not to iterate the
> lengthy cast.

Thank you for the quick and clear explanation!

I'll apply these changes in the next version.

Appreciate it!


  reply	other threads:[~2025-09-26  4:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-25  2:16 [PATCH net-next v6 0/3] net: Avoid ehash lookup races xuanqiang.luo
2025-09-25  2:16 ` [PATCH net-next v6 1/3] rculist: Add hlist_nulls_replace_rcu() and hlist_nulls_replace_init_rcu() xuanqiang.luo
2025-09-25 17:56   ` Kuniyuki Iwashima
2025-09-26  3:23     ` luoxuanqiang
2025-09-26  4:02       ` Kuniyuki Iwashima
2025-09-26  4:33         ` luoxuanqiang [this message]
2025-09-25  2:16 ` [PATCH net-next v6 2/3] inet: Avoid ehash lookup race in inet_ehash_insert() xuanqiang.luo
2025-09-25 18:00   ` Kuniyuki Iwashima
2025-09-26  3:24     ` luoxuanqiang
2025-09-25  2:16 ` [PATCH net-next v6 3/3] inet: Avoid ehash lookup race in inet_twsk_hashdance_schedule() xuanqiang.luo
2025-09-25 18:22   ` Kuniyuki Iwashima
2025-09-26  3:25     ` luoxuanqiang

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=15ce9ffb-fdd0-4dba-8cfa-b24de99368fb@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=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).