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, kuni1840@gmail.com,
netdev@vger.kernel.org
Subject: Re: [PATCH v3 net-next 0/2] tcp: Make simultaneous connect() RFC-compliant.
Date: Sat, 13 Jul 2024 22:30:30 +0000 [thread overview]
Message-ID: <172090983097.21567.15657611491994442725.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240710171246.87533-1-kuniyu@amazon.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 10 Jul 2024 10:12:44 -0700 you wrote:
> Patch 1 fixes an issue that BPF TCP option parser is triggered for ACK
> instead of SYN+ACK in the case of simultaneous connect().
>
> Patch 2 removes an wrong assumption in tcp_ao/self-connnect tests.
>
> v3:
> * Use (sk->sk_state == TCP_SYN_RECV && sk->sk_socket) to detect cross SYN case
>
> [...]
Here is the summary with links:
- [v3,net-next,1/2] tcp: Don't drop SYN+ACK for simultaneous connect().
https://git.kernel.org/netdev/net-next/c/23e89e8ee7be
- [v3,net-next,2/2] selftests: tcp: Remove broken SNMP assumptions for TCP AO self-connect tests.
https://git.kernel.org/netdev/net-next/c/b3bb4d23a41b
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:[~2024-07-13 22:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 17:12 [PATCH v3 net-next 0/2] tcp: Make simultaneous connect() RFC-compliant Kuniyuki Iwashima
2024-07-10 17:12 ` [PATCH v3 net-next 1/2] tcp: Don't drop SYN+ACK for simultaneous connect() Kuniyuki Iwashima
2024-07-11 15:34 ` Eric Dumazet
2024-07-15 15:58 ` Matthieu Baerts
2024-07-16 19:23 ` Kuniyuki Iwashima
2024-07-16 20:04 ` Matthieu Baerts
2024-07-16 20:28 ` Kuniyuki Iwashima
2024-07-10 17:12 ` [PATCH v3 net-next 2/2] selftests: tcp: Remove broken SNMP assumptions for TCP AO self-connect tests Kuniyuki Iwashima
2024-07-13 22:30 ` 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=172090983097.21567.15657611491994442725.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.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.