From: Paolo Abeni <pabeni@redhat.com>
To: Philo Lu <lulie@linux.alibaba.com>, netdev@vger.kernel.org
Cc: willemdebruijn.kernel@gmail.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, dsahern@kernel.org,
antony.antony@secunet.com, steffen.klassert@secunet.com,
linux-kernel@vger.kernel.org, dust.li@linux.alibaba.com,
jakub@cloudflare.com, fred.cc@alibaba-inc.com,
yubing.qiuyubing@alibaba-inc.com
Subject: Re: [PATCH v5 net-next 3/3] ipv4/udp: Add 4-tuple hash for connected socket
Date: Thu, 24 Oct 2024 17:01:28 +0200 [thread overview]
Message-ID: <b232a642-2f0d-4bac-9bcf-50d653ea875d@redhat.com> (raw)
In-Reply-To: <20241018114535.35712-4-lulie@linux.alibaba.com>
On 10/18/24 13:45, Philo Lu wrote:
[...]
> +/* In hash4, rehash can also happen in connect(), where hash4_cnt keeps unchanged. */
> +static void udp4_rehash4(struct udp_table *udptable, struct sock *sk, u16 newhash4)
> +{
> + struct udp_hslot *hslot4, *nhslot4;
> +
> + hslot4 = udp_hashslot4(udptable, udp_sk(sk)->udp_lrpa_hash);
> + nhslot4 = udp_hashslot4(udptable, newhash4);
> + udp_sk(sk)->udp_lrpa_hash = newhash4;
> +
> + if (hslot4 != nhslot4) {
> + spin_lock_bh(&hslot4->lock);
> + hlist_del_init_rcu(&udp_sk(sk)->udp_lrpa_node);
> + hslot4->count--;
> + spin_unlock_bh(&hslot4->lock);
> +
> + synchronize_rcu();
This deserve a comment explaining why it's needed. I had to dig in past
revision to understand it.
> +
> + spin_lock_bh(&nhslot4->lock);
> + hlist_add_head_rcu(&udp_sk(sk)->udp_lrpa_node, &nhslot4->head);
> + nhslot4->count++;
> + spin_unlock_bh(&nhslot4->lock);
> + }
> +}
> +
> +static void udp4_unhash4(struct udp_table *udptable, struct sock *sk)
> +{
> + struct udp_hslot *hslot2, *hslot4;
> +
> + if (udp_hashed4(sk)) {
> + hslot2 = udp_hashslot2(udptable, udp_sk(sk)->udp_portaddr_hash);
> + hslot4 = udp_hashslot4(udptable, udp_sk(sk)->udp_lrpa_hash);
> +
> + spin_lock(&hslot4->lock);
> + hlist_del_init_rcu(&udp_sk(sk)->udp_lrpa_node);
> + hslot4->count--;
> + spin_unlock(&hslot4->lock);
> +
> + spin_lock(&hslot2->lock);
> + udp_hash4_dec(hslot2);
> + spin_unlock(&hslot2->lock);
> + }
> +}
> +
> +/* call with sock lock */
> +static void udp4_hash4(struct sock *sk)
> +{
> + struct udp_hslot *hslot, *hslot2, *hslot4;
> + struct net *net = sock_net(sk);
> + struct udp_table *udptable;
> + unsigned int hash;
> +
> + if (sk_unhashed(sk) || inet_sk(sk)->inet_rcv_saddr == htonl(INADDR_ANY))
> + return;
> +
> + hash = udp_ehashfn(net, inet_sk(sk)->inet_rcv_saddr, inet_sk(sk)->inet_num,
> + inet_sk(sk)->inet_daddr, inet_sk(sk)->inet_dport);
> +
> + udptable = net->ipv4.udp_table;
> + if (udp_hashed4(sk)) {
> + udp4_rehash4(udptable, sk, hash);
It's unclear to me how we can enter this branch. Also it's unclear why
here you don't need to call udp_hash4_inc()udp_hash4_dec, too. Why such
accounting can't be placed in udp4_rehash4()?
[...]
> @@ -2031,6 +2180,19 @@ void udp_lib_rehash(struct sock *sk, u16 newhash)
> spin_unlock(&nhslot2->lock);
> }
>
> + if (udp_hashed4(sk)) {
> + udp4_rehash4(udptable, sk, newhash4);
> +
> + if (hslot2 != nhslot2) {
> + spin_lock(&hslot2->lock);
> + udp_hash4_dec(hslot2);
> + spin_unlock(&hslot2->lock);
> +
> + spin_lock(&nhslot2->lock);
> + udp_hash4_inc(nhslot2);
> + spin_unlock(&nhslot2->lock);
> + }
> + }
> spin_unlock_bh(&hslot->lock);
The udp4_rehash4() call above is in atomic context and could end-up
calling synchronize_rcu() which is a blocking function. You must avoid that.
Cheers,
Paolo
next prev parent reply other threads:[~2024-10-24 15:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 11:45 [PATCH v5 net-next 0/3] udp: Add 4-tuple hash for connected sockets Philo Lu
2024-10-18 11:45 ` [PATCH v5 net-next 1/3] net/udp: Add a new struct for hash2 slot Philo Lu
2024-10-24 14:31 ` Paolo Abeni
2024-10-24 14:38 ` Paolo Abeni
2024-10-18 11:45 ` [PATCH v5 net-next 2/3] net/udp: Add 4-tuple hash list basis Philo Lu
2024-10-18 11:45 ` [PATCH v5 net-next 3/3] ipv4/udp: Add 4-tuple hash for connected socket Philo Lu
2024-10-24 15:01 ` Paolo Abeni [this message]
2024-10-24 15:04 ` Paolo Abeni
2024-10-25 3:50 ` Philo Lu
2024-10-25 9:02 ` Paolo Abeni
2024-10-26 1:39 ` Philo Lu
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=b232a642-2f0d-4bac-9bcf-50d653ea875d@redhat.com \
--to=pabeni@redhat.com \
--cc=antony.antony@secunet.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=dust.li@linux.alibaba.com \
--cc=edumazet@google.com \
--cc=fred.cc@alibaba-inc.com \
--cc=jakub@cloudflare.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lulie@linux.alibaba.com \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
--cc=willemdebruijn.kernel@gmail.com \
--cc=yubing.qiuyubing@alibaba-inc.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
all inboxes | Powered by JetHome®