From: patchwork-bot+netdevbpf@kernel.org
To: Kuniyuki Iwashima <kuniyu@amazon.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, dsahern@kernel.org, joannelkoong@gmail.com,
kuni1840@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH v2 net 0/6] tcp: Fix bind() regression for v4-mapped-v6 address
Date: Wed, 13 Sep 2023 06:20:27 +0000 [thread overview]
Message-ID: <169458602717.26932.15402915651770766625.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230911183700.60878-1-kuniyu@amazon.com>
Hello:
This series was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Mon, 11 Sep 2023 11:36:54 -0700 you wrote:
> Since bhash2 was introduced, bind() is broken in two cases related
> to v4-mapped-v6 address.
>
> This series fixes the regression and adds test to cover the cases.
>
>
> Changes:
> v2:
> * Added patch 1 to factorise duplicated comparison (Eric Dumazet)
>
> [...]
Here is the summary with links:
- [v2,net,1/6] tcp: Factorise sk_family-independent comparison in inet_bind2_bucket_match(_addr_any).
https://git.kernel.org/netdev/net/c/c6d277064b1d
- [v2,net,2/6] tcp: Fix bind() regression for v4-mapped-v6 wildcard address.
https://git.kernel.org/netdev/net/c/aa99e5f87bd5
- [v2,net,3/6] tcp: Fix bind() regression for v4-mapped-v6 non-wildcard address.
https://git.kernel.org/netdev/net/c/c48ef9c4aed3
- [v2,net,4/6] selftest: tcp: Fix address length in bind_wildcard.c.
https://git.kernel.org/netdev/net/c/0071d15517b4
- [v2,net,5/6] selftest: tcp: Move expected_errno into each test case in bind_wildcard.c.
https://git.kernel.org/netdev/net/c/2895d879dd41
- [v2,net,6/6] selftest: tcp: Add v4-mapped-v6 cases in bind_wildcard.c.
https://git.kernel.org/netdev/net/c/8637d8e8b653
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-09-13 6:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 18:36 [PATCH v2 net 0/6] tcp: Fix bind() regression for v4-mapped-v6 address Kuniyuki Iwashima
2023-09-11 18:36 ` [PATCH v2 net 1/6] tcp: Factorise sk_family-independent comparison in inet_bind2_bucket_match(_addr_any) Kuniyuki Iwashima
2023-09-12 4:48 ` Eric Dumazet
2023-09-11 18:36 ` [PATCH v2 net 2/6] tcp: Fix bind() regression for v4-mapped-v6 wildcard address Kuniyuki Iwashima
2023-09-12 4:58 ` Eric Dumazet
2023-09-11 18:36 ` [PATCH v2 net 3/6] tcp: Fix bind() regression for v4-mapped-v6 non-wildcard address Kuniyuki Iwashima
2023-09-12 4:59 ` Eric Dumazet
2023-09-12 7:25 ` Andrei Vagin
2023-09-12 7:59 ` Kuniyuki Iwashima
2023-09-12 14:29 ` Andrei Vagin
2023-09-11 18:36 ` [PATCH v2 net 4/6] selftest: tcp: Fix address length in bind_wildcard.c Kuniyuki Iwashima
2023-09-11 18:36 ` [PATCH v2 net 5/6] selftest: tcp: Move expected_errno into each test case " Kuniyuki Iwashima
2023-09-11 18:37 ` [PATCH v2 net 6/6] selftest: tcp: Add v4-mapped-v6 cases " Kuniyuki Iwashima
2023-09-11 18:54 ` [PATCH v2 net 0/6] tcp: Fix bind() regression for v4-mapped-v6 address Martin KaFai Lau
2023-09-13 6:20 ` patchwork-bot+netdevbpf [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=169458602717.26932.15402915651770766625.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=joannelkoong@gmail.com \
--cc=kuba@kernel.org \
--cc=kuni1840@gmail.com \
--cc=kuniyu@amazon.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 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.