From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: <david.laight.linux@gmail.com>
Cc: <davem@davemloft.net>, <dsahern@kernel.org>,
<edumazet@google.com>, <horms@kernel.org>, <krisman@suse.de>,
<kuba@kernel.org>, <kuniyu@amazon.com>,
<linux-kernel@vger.kernel.org>, <lmb@isovalent.com>,
<netdev@vger.kernel.org>, <pabeni@redhat.com>,
<tom@herbertland.com>
Subject: Re: [PATCH net 1/2] udp4: Rescan udp hash chains if cross-linked.
Date: Mon, 27 Jan 2025 12:33:04 -0800 [thread overview]
Message-ID: <20250127203304.65501-1-kuniyu@amazon.com> (raw)
In-Reply-To: <20250127194024.3647-2-david.laight.linux@gmail.com>
From: David Laight <david.laight.linux@gmail.com>
Date: Mon, 27 Jan 2025 19:40:23 +0000
> udp_lib_rehash() can get called at any time and will move a
> socket to a different hash2 chain.
> This can cause udp4_lib_lookup2() (processing incoming UDP) to
> fail to find a socket and an ICMP port unreachable be sent.
>
> Prior to ca065d0cf80fa the lookup used 'hlist_nulls' and checked
> that the 'end if list' marker was on the correct list.
I think we should use hlist_nulls for hash2 as hash4.
---8<---
commit dab78a1745ab3c6001e1e4d50a9d09efef8e260d
Author: Philo Lu <lulie@linux.alibaba.com>
Date: Thu Nov 14 18:52:05 2024 +0800
net/udp: Add 4-tuple hash list basis
...
hash4 uses hlist_nulls to avoid moving wrongly onto another hlist due to
concurrent rehash, because rehash() can happen with lookup().
---8<---
Also, Fixes: tag is missing in both patches.
>
> Signed-off-by: David Laight <david.laight.linux@gmail.com>
> ---
> net/ipv4/udp.c | 19 +++++++++++++++++--
> 1 file changed, 17 insertions(+), 2 deletions(-)
>
> diff --git a/net/ipv4/udp.c b/net/ipv4/udp.c
> index 86d282618515..a8e2b431d348 100644
> --- a/net/ipv4/udp.c
> +++ b/net/ipv4/udp.c
> @@ -425,16 +425,21 @@ static struct sock *udp4_lib_lookup2(const struct net *net,
> __be32 saddr, __be16 sport,
> __be32 daddr, unsigned int hnum,
> int dif, int sdif,
> + unsigned int hash2, unsigned int mask,
> struct udp_hslot *hslot2,
> struct sk_buff *skb)
> {
> + unsigned int hash2_rescan;
> struct sock *sk, *result;
> int score, badness;
> bool need_rescore;
>
> +rescan:
> + hash2_rescan = hash2;
> result = NULL;
> badness = 0;
> udp_portaddr_for_each_entry_rcu(sk, &hslot2->head) {
> + hash2_rescan = udp_sk(sk)->udp_portaddr_hash;
> need_rescore = false;
> rescore:
> score = compute_score(need_rescore ? result : sk, net, saddr,
> @@ -475,6 +480,16 @@ static struct sock *udp4_lib_lookup2(const struct net *net,
> goto rescore;
> }
> }
> +
> + /* udp sockets can get moved to a different hash chain.
> + * If the chains have got crossed then rescan.
> + */
nit: trailing spaces here ^^^^^^^^
> + if ((hash2_rescan ^ hash2) & mask) {
> + /* Ensure hslot2->head is reread */
> + barrier();
> + goto rescan;
> + }
> +
> return result;
> }
>
> @@ -654,7 +669,7 @@ struct sock *__udp4_lib_lookup(const struct net *net, __be32 saddr,
> /* Lookup connected or non-wildcard socket */
> result = udp4_lib_lookup2(net, saddr, sport,
> daddr, hnum, dif, sdif,
> - hslot2, skb);
> + hash2, udptable->mask, hslot2, skb);
> if (!IS_ERR_OR_NULL(result) && result->sk_state == TCP_ESTABLISHED)
> goto done;
>
> @@ -680,7 +695,7 @@ struct sock *__udp4_lib_lookup(const struct net *net, __be32 saddr,
>
> result = udp4_lib_lookup2(net, saddr, sport,
> htonl(INADDR_ANY), hnum, dif, sdif,
> - hslot2, skb);
> + hash2, udptable->mask, hslot2, skb);
> done:
> if (IS_ERR(result))
> return NULL;
> --
> 2.39.5
>
next prev parent reply other threads:[~2025-01-27 20:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-27 19:40 [PATCH net 0/2] udplookup: Rescan udp hash chains if cross-linked David Laight
2025-01-27 19:40 ` [PATCH net 1/2] udp4: " David Laight
2025-01-27 19:40 ` [PATCH net 2/2] udp6: " David Laight
2025-01-27 20:33 ` Kuniyuki Iwashima [this message]
2025-01-27 21:26 ` [PATCH net 1/2] udp4: " David Laight
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=20250127203304.65501-1-kuniyu@amazon.com \
--to=kuniyu@amazon.com \
--cc=davem@davemloft.net \
--cc=david.laight.linux@gmail.com \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=krisman@suse.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lmb@isovalent.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tom@herbertland.com \
/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).