From: patchwork-bot+netdevbpf@kernel.org
To: Simon Baatz <gmbnomis@gmail.com>
Cc: edumazet@google.com, ncardwell@google.com, kuniyu@google.com,
davem@davemloft.net, dsahern@kernel.org, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, shuah@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net v2 0/2] tcp: re-enable acceptance of FIN packets when RWIN is 0
Date: Thu, 26 Feb 2026 03:10:13 +0000 [thread overview]
Message-ID: <177207541303.1014739.8301517056403543881.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260224-fix_zero_wnd_fin-v2-0-a16677ea7cea@gmail.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 24 Feb 2026 09:20:11 +0100 you wrote:
> Hi,
>
> this series restores the ability to accept in‑sequence FIN packets
> even when the advertised receive window is zero, and adds a
> packetdrill test to guard the behavior.
>
> Signed-off-by: Simon Baatz <gmbnomis@gmail.com>
>
> [...]
Here is the summary with links:
- [net,v2,1/2] tcp: re-enable acceptance of FIN packets when RWIN is 0
https://git.kernel.org/netdev/net/c/1e3bb184e941
- [net,v2,2/2] selftests/net: packetdrill: Verify acceptance of FIN packets when RWIN is 0
https://git.kernel.org/netdev/net/c/745113323098
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-02-26 3:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 8:20 [PATCH net v2 0/2] tcp: re-enable acceptance of FIN packets when RWIN is 0 Simon Baatz via B4 Relay
2026-02-24 8:20 ` [PATCH net v2 1/2] " Simon Baatz via B4 Relay
2026-02-24 10:22 ` Eric Dumazet
2026-02-25 6:29 ` Kuniyuki Iwashima
2026-02-24 8:20 ` [PATCH net v2 2/2] selftests/net: packetdrill: Verify " Simon Baatz via B4 Relay
2026-02-24 10:23 ` Eric Dumazet
2026-02-25 6:30 ` Kuniyuki Iwashima
2026-02-26 3:10 ` 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=177207541303.1014739.8301517056403543881.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=gmbnomis@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.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