From: patchwork-bot+netdevbpf@kernel.org
To: Esko Mobius <echoowall@gmail.com>
Cc: netdev@vger.kernel.org, kuba@kernel.org, pabeni@redhat.com,
davem@davemloft.net, horms@kernel.org, dsahern@kernel.org,
idosch@nvidia.com, jiayuan.chen@linux.dev, shuah@kernel.org,
regressions@leemhuis.info, regressions@lists.linux.dev,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, edumazet@kernel.org
Subject: Re: [PATCH net 0/2] Revert advertising the TCP MSS from the configured MTU
Date: Wed, 28 Oct 2026 23:10:05 +0000 [thread overview]
Message-ID: <179322900582.1471258.8439548147927472759.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261026-advmss-revert-v1-0-272fa4b7ecb6@gmail.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 26 Oct 2026 15:23:07 +0800 you wrote:
> Commit 2640e6419594 ("net: advertise TCP MSS from the configured MTU,
> not the learned PMTU") breaks TCP for clients behind networks that
> filter inbound ICMP, when the server reaches them through a hop with a
> smaller MTU: the handshake completes, then the connection stalls as
> soon as the client sends full-size segments. This was reported in [1]
> and confirmed on 7.3-rc7; reverting the commit on top of 7.3-rc7 fixes
> it. Details and numbers are in patch 2.
>
> [...]
Here is the summary with links:
- [net,1/2] Revert "selftests: net: packetdrill: add tests for advertised MSS with PMTU exceptions"
https://git.kernel.org/netdev/net/c/b4aac29a21d9
- [net,2/2] Revert "net: advertise TCP MSS from the configured MTU, not the learned PMTU"
https://git.kernel.org/netdev/net/c/564313447e54
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-10-28 23:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 7:23 [PATCH net 0/2] Revert advertising the TCP MSS from the configured MTU Esko Mobius
2026-10-26 7:23 ` Esko Mobius via B4 Relay
2026-10-26 7:23 ` [PATCH net 1/2] Revert "selftests: net: packetdrill: add tests for advertised MSS with PMTU exceptions" Esko Mobius
2026-10-26 7:23 ` Esko Mobius via B4 Relay
2026-10-27 11:44 ` Jiayuan Chen
2026-10-26 7:23 ` [PATCH net 2/2] Revert "net: advertise TCP MSS from the configured MTU, not the learned PMTU" Esko Mobius
2026-10-26 7:23 ` Esko Mobius via B4 Relay
2026-10-27 12:45 ` Jiayuan Chen
2026-10-27 13:02 ` Eric Dumazet
2026-10-27 13:12 ` Esko Mobius
2026-10-27 13:44 ` Jiayuan Chen
2026-10-27 23:18 ` Jakub Kicinski
2026-10-28 3:38 ` Esko Mobius
2026-10-28 22:52 ` Jakub Kicinski
2026-10-29 10:18 ` David Laight
2026-10-29 10:21 ` Esko Mobius
2026-10-29 11:20 ` David Laight
2026-10-29 12:36 ` Esko Mobius
2026-10-26 13:28 ` [PATCH net 0/2] Revert advertising the TCP MSS from the configured MTU Eric Dumazet
2026-10-28 23: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=179322900582.1471258.8439548147927472759.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=echoowall@gmail.com \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=jiayuan.chen@linux.dev \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=shuah@kernel.org \
--cc=stable@vger.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 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.