From: luoxuanqiang <xuanqiang.luo@linux.dev>
To: Kuniyuki Iwashima <kuniyu@google.com>
Cc: edumazet@google.com, kerneljasonxing@gmail.com,
davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
Xuanqiang Luo <luoxuanqiang@kylinos.cn>
Subject: Re: [PATCH net-next v3 3/3] inet: Avoid ehash lookup race in inet_twsk_hashdance_schedule()
Date: Thu, 18 Sep 2025 16:32:32 +0800 [thread overview]
Message-ID: <c7a91e0c-b575-43b3-af5b-64fc35b46fac@linux.dev> (raw)
In-Reply-To: <CAAVpQUBY=h3gDfaX=J9vbSuhYTn8cfCsBGhPLqoer0OSYdihDg@mail.gmail.com>
在 2025/9/17 12:36, Kuniyuki Iwashima 写道:
> On Tue, Sep 16, 2025 at 8:27 PM luoxuanqiang <xuanqiang.luo@linux.dev> wrote:
>>
>> 在 2025/9/17 03:48, Kuniyuki Iwashima 写道:
>>> On Tue, Sep 16, 2025 at 3:31 AM <xuanqiang.luo@linux.dev> wrote:
>>>> From: Xuanqiang Luo <luoxuanqiang@kylinos.cn>
>>>>
>>>> Since ehash lookups are lockless, if another CPU is converting sk to tw
>>>> concurrently, fetching the newly inserted tw with tw->tw_refcnt == 0 cause
>>>> lookup failure.
>>>>
>>>> The call trace map is drawn as follows:
>>>> CPU 0 CPU 1
>>>> ----- -----
>>>> inet_twsk_hashdance_schedule()
>>>> spin_lock()
>>>> inet_twsk_add_node_rcu(tw, ...)
>>>> __inet_lookup_established()
>>>> (find tw, failure due to tw_refcnt = 0)
>>>> __sk_nulls_del_node_init_rcu(sk)
>>>> refcount_set(&tw->tw_refcnt, 3)
>>>> spin_unlock()
>>>>
>>>> By replacing sk with tw atomically via hlist_nulls_replace_init_rcu() after
>>>> setting tw_refcnt, we ensure that tw is either fully initialized or not
>>>> visible to other CPUs, eliminating the race.
>>>>
>>>> Fixes: 3ab5aee7fe84 ("net: Convert TCP & DCCP hash tables to use RCU / hlist_nulls")
>>>> Signed-off-by: Xuanqiang Luo <luoxuanqiang@kylinos.cn>
>>>> ---
>>>> net/ipv4/inet_timewait_sock.c | 15 ++++++---------
>>>> 1 file changed, 6 insertions(+), 9 deletions(-)
>>>>
>>>> diff --git a/net/ipv4/inet_timewait_sock.c b/net/ipv4/inet_timewait_sock.c
>>>> index 5b5426b8ee92..1ba20c4cb73b 100644
>>>> --- a/net/ipv4/inet_timewait_sock.c
>>>> +++ b/net/ipv4/inet_timewait_sock.c
>>>> @@ -116,7 +116,7 @@ void inet_twsk_hashdance_schedule(struct inet_timewait_sock *tw,
>>>> spinlock_t *lock = inet_ehash_lockp(hashinfo, sk->sk_hash);
>>>> struct inet_bind_hashbucket *bhead, *bhead2;
>>>>
>>>> - /* Step 1: Put TW into bind hash. Original socket stays there too.
>>>> + /* Put TW into bind hash. Original socket stays there too.
>>>> Note, that any socket with inet->num != 0 MUST be bound in
>>>> binding cache, even if it is closed.
>>>> */
>>>> @@ -140,14 +140,6 @@ void inet_twsk_hashdance_schedule(struct inet_timewait_sock *tw,
>>>>
>>>> spin_lock(lock);
>>>>
>>>> - /* Step 2: Hash TW into tcp ehash chain */
>>>> - inet_twsk_add_node_rcu(tw, &ehead->chain);
>>>> -
>>>> - /* Step 3: Remove SK from hash chain */
>>>> - if (__sk_nulls_del_node_init_rcu(sk))
>>>> - sock_prot_inuse_add(sock_net(sk), sk->sk_prot, -1);
>>>> -
>>>> -
>>>> /* Ensure above writes are committed into memory before updating the
>>>> * refcount.
>>>> * Provides ordering vs later refcount_inc().
>>>> @@ -162,6 +154,11 @@ void inet_twsk_hashdance_schedule(struct inet_timewait_sock *tw,
>>>> */
>>>> refcount_set(&tw->tw_refcnt, 3);
>>>>
>>>> + if (hlist_nulls_replace_init_rcu(&sk->sk_nulls_node, &tw->tw_node))
>>>> + sock_prot_inuse_add(sock_net(sk), sk->sk_prot, -1);
>>>> + else
>>>> + inet_twsk_add_node_rcu(tw, &ehead->chain);
>>> When hlist_nulls_replace_init_rcu() returns false ?
>> When hlist_nulls_replace_init_rcu() returns false, it means
>> sk is unhashed,
> and how does this happen ?
>
> Here is under lock_sock() I think, for example, you can
> find a lockdep annotation in the path:
>
> tcp_time_wait_init
> tp->af_specific->md5_lookup / tcp_v4_md5_lookup
> tcp_md5_do_lookup
> __tcp_md5_do_lookup
> rcu_dereference_check(tp->md5sig_info, lockdep_sock_is_held(sk));
>
> So, is there a path that unhashes socket without holding
> lock_sock() ?
>
I'm not entirely sure about this point yet, because
inet_unhash() is called in too many places and uses
__sk_nulls_del_node_init_rcu() to unhash sockets without
explicitly requiring bh_lock_sock().
Until I can verify this, I'll keep the original check
for old socket unhashed state to ensure safety.
It would be great if you could confirm this behavior.
Thanks
Xuanqiang.
>> the replacement operation failed, we need
>> to insert tw, and this doesn't change the original logic.
>>
>>>> +
>>>> inet_twsk_schedule(tw, timeo);
>>>>
>>>> spin_unlock(lock);
>>>> --
>>>> 2.25.1
>>>>
next prev parent reply other threads:[~2025-09-18 8:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 10:30 [PATCH net-next v3 0/3] net: Avoid ehash lookup races xuanqiang.luo
2025-09-16 10:30 ` [PATCH net-next v3 1/3] rculist: Add __hlist_nulls_replace_rcu() and hlist_nulls_replace_init_rcu() xuanqiang.luo
2025-09-16 18:58 ` Kuniyuki Iwashima
2025-09-17 3:26 ` luoxuanqiang
2025-09-17 4:27 ` Kuniyuki Iwashima
2025-09-17 4:43 ` Kuniyuki Iwashima
2025-09-18 6:09 ` luoxuanqiang
2025-09-18 6:09 ` luoxuanqiang
2025-09-16 10:30 ` [PATCH net-next v3 2/3] inet: Avoid ehash lookup race in inet_ehash_insert() xuanqiang.luo
2025-09-16 10:30 ` [PATCH net-next v3 3/3] inet: Avoid ehash lookup race in inet_twsk_hashdance_schedule() xuanqiang.luo
2025-09-16 19:48 ` Kuniyuki Iwashima
2025-09-17 3:26 ` luoxuanqiang
2025-09-17 4:36 ` Kuniyuki Iwashima
2025-09-18 8:32 ` luoxuanqiang [this message]
2025-09-19 8:38 ` Kuniyuki Iwashima
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=c7a91e0c-b575-43b3-af5b-64fc35b46fac@linux.dev \
--to=xuanqiang.luo@linux.dev \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kerneljasonxing@gmail.com \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=luoxuanqiang@kylinos.cn \
--cc=netdev@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.