From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: <borrello@diag.uniroma1.it>
Cc: <c.giuffrida@vu.nl>, <davem@davemloft.net>, <dsahern@kernel.org>,
<edumazet@google.com>, <h.j.bos@vu.nl>, <jkl820.git@gmail.com>,
<kuba@kernel.org>, <linux-kernel@vger.kernel.org>,
<netdev@vger.kernel.org>, <pabeni@redhat.com>,
<yoshfuji@linux-ipv6.org>, <kuniyu@amazon.com>
Subject: Re: [PATCH] inet: fix fast path in __inet_hash_connect()
Date: Fri, 13 Jan 2023 09:48:13 +0900 [thread overview]
Message-ID: <20230113004813.82874-1-kuniyu@amazon.com> (raw)
In-Reply-To: <20230112-inet_hash_connect_bind_head-v1-1-7e3c770157c8@diag.uniroma1.it>
From: Pietro Borrello <borrello@diag.uniroma1.it>
Date: Thu, 12 Jan 2023 15:39:23 +0000
> __inet_hash_connect() has a fast path taken if sk_head(&tb->owners) is
> equal to the sk parameter.
> sk_head() returns the list_entry() with respect to the sk_node field.
nit: s/list_entry/hlist_entry/
> However entries in the tb->owners list are inserted with respect to the
> sk_bind_node field with sk_add_bind_node().
> Thus the check would never pass and the fast path never execute.
>
> Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
> Signed-off-by: Pietro Borrello <borrello@diag.uniroma1.it>
Good catch!
Other than the nit above, looks good to me.
Reviewed-by: Kuniyuki Iwashima <kuniyu@amazon.com>
Thank you.
> ---
> include/net/sock.h | 10 ++++++++++
> net/ipv4/inet_hashtables.c | 2 +-
> 2 files changed, 11 insertions(+), 1 deletion(-)
>
> diff --git a/include/net/sock.h b/include/net/sock.h
> index dcd72e6285b2..23fc403284db 100644
> --- a/include/net/sock.h
> +++ b/include/net/sock.h
> @@ -860,6 +860,16 @@ static inline void sk_nulls_add_node_rcu(struct sock *sk, struct hlist_nulls_hea
> __sk_nulls_add_node_rcu(sk, list);
> }
>
> +static inline struct sock *__sk_bind_head(const struct hlist_head *head)
> +{
> + return hlist_entry(head->first, struct sock, sk_bind_node);
> +}
> +
> +static inline struct sock *sk_bind_head(const struct hlist_head *head)
> +{
> + return hlist_empty(head) ? NULL : __sk_bind_head(head);
> +}
> +
> static inline void __sk_del_bind_node(struct sock *sk)
> {
> __hlist_del(&sk->sk_bind_node);
> diff --git a/net/ipv4/inet_hashtables.c b/net/ipv4/inet_hashtables.c
> index d039b4e732a3..a805e086fb48 100644
> --- a/net/ipv4/inet_hashtables.c
> +++ b/net/ipv4/inet_hashtables.c
> @@ -998,7 +998,7 @@ int __inet_hash_connect(struct inet_timewait_death_row *death_row,
> hinfo->bhash_size)];
> tb = inet_csk(sk)->icsk_bind_hash;
> spin_lock_bh(&head->lock);
> - if (sk_head(&tb->owners) == sk && !sk->sk_bind_node.next) {
> + if (sk_bind_head(&tb->owners) == sk && !sk->sk_bind_node.next) {
> inet_ehash_nolisten(sk, NULL, NULL);
> spin_unlock_bh(&head->lock);
> return 0;
>
> ---
> base-commit: 1b929c02afd37871d5afb9d498426f83432e71c2
> change-id: 20230112-inet_hash_connect_bind_head-8f2dc98f08b1
>
> Best regards,
> --
> Pietro Borrello <borrello@diag.uniroma1.it>
prev parent reply other threads:[~2023-01-13 0:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 15:39 Pietro Borrello
2023-01-13 0:48 ` Kuniyuki Iwashima [this message]
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=20230113004813.82874-1-kuniyu@amazon.com \
--to=kuniyu@amazon.com \
--cc=borrello@diag.uniroma1.it \
--cc=c.giuffrida@vu.nl \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=h.j.bos@vu.nl \
--cc=jkl820.git@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yoshfuji@linux-ipv6.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
all inboxes | Powered by JetHome®