From: Kuniyuki Iwashima <kuniyu@amazon•com>
To: "David S. Miller" <davem@davemloft•net>,
Eric Dumazet <edumazet@google•com>,
Jakub Kicinski <kuba@kernel•org>, Paolo Abeni <pabeni@redhat•com>,
David Ahern <dsahern@kernel•org>
Cc: Kuniyuki Iwashima <kuniyu@amazon•com>,
Kuniyuki Iwashima <kuni1840@gmail•com>, <netdev@vger•kernel.org>
Subject: [PATCH v3 net-next 0/2] tcp: Make simultaneous connect() RFC-compliant.
Date: Wed, 10 Jul 2024 10:12:44 -0700 [thread overview]
Message-ID: <20240710171246.87533-1-kuniyu@amazon.com> (raw)
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
v2: https://lore.kernel.org/netdev/20240708180852.92919-1-kuniyu@amazon.com/
* Target net-next and remove Fixes: tag
* Don't skip bpf_skops_parse_hdr() to centralise sk_state check
* Remove unnecessary ACK after SYN+ACK
* Add patch 2
v1: https://lore.kernel.org/netdev/20240704035703.95065-1-kuniyu@amazon.com/
Kuniyuki Iwashima (2):
tcp: Don't drop SYN+ACK for simultaneous connect().
selftests: tcp: Remove broken SNMP assumptions for TCP AO self-connect
tests.
net/ipv4/tcp_input.c | 9 +++++++++
.../selftests/net/tcp_ao/self-connect.c | 18 ------------------
2 files changed, 9 insertions(+), 18 deletions(-)
--
2.30.2
next reply other threads:[~2024-07-10 17:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 17:12 Kuniyuki Iwashima [this message]
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 ` [PATCH v3 net-next 0/2] tcp: Make simultaneous connect() RFC-compliant patchwork-bot+netdevbpf
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=20240710171246.87533-1-kuniyu@amazon.com \
--to=kuniyu@amazon$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=dsahern@kernel$(echo .)org \
--cc=edumazet@google$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=kuni1840@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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