From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
ncardwell@google.com, kuniyu@google.com, horms@kernel.org,
flavius.mazilu@stud.acs.upb.ro, tuexen@fh-muenster.de,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] tcp: do not accept ACK of our ISS on active opens
Date: Sat, 21 Nov 2026 01:20:10 +0000 [thread overview]
Message-ID: <179522401027.873873.9137118400296045450.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261118172654.1267071-1-edumazet@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 18 Nov 2026 18:26:52 +0100 you wrote:
> Michael Tuexen asked on the tcpm list whether, after a completed
> handshake, a segment with SEG.ACK == ISS is a duplicate ACK or a ghost
> ACK [1]. Flavius-Romeo Mazilu noted that Linux gives a different answer
> on each side of the connection [2]: passive opens send a challenge ACK,
> active opens silently accept the segment.
>
> The first patch makes active opens (including Fast Open and
> simultaneous opens) behave like passive ones, without changing
> the value of tcpi_bytes_acked seen by user space and BPF.
>
> [...]
Here is the summary with links:
- [net-next,1/2] tcp: do not accept ACK of our ISS on active opens
https://git.kernel.org/netdev/net-next/c/a25df726c715
- [net-next,2/2] selftests/net: packetdrill: add tests for ACK of ISS
https://git.kernel.org/netdev/net-next/c/5fa71aea9d59
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:[~2026-11-21 1:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-18 17:26 [PATCH net-next 0/2] tcp: do not accept ACK of our ISS on active opens Eric Dumazet
2026-11-18 17:26 ` [PATCH net-next 1/2] " Eric Dumazet
2026-11-18 17:26 ` [PATCH net-next 2/2] selftests/net: packetdrill: add tests for ACK of ISS Eric Dumazet
2026-11-21 1: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=179522401027.873873.9137118400296045450.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=flavius.mazilu@stud.acs.upb.ro \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tuexen@fh-muenster.de \
/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