diff options
| author | Jakub Kicinski <kuba@kernel.org> | 2026-10-28 15:50:44 -0700 |
|---|---|---|
| committer | Jakub Kicinski <kuba@kernel.org> | 2026-10-28 15:51:49 -0700 |
| commit | fd1436a75ceb07c7029be02f89e8a1b34a6978c8 (patch) | |
| tree | 56b23214027a9e531e9da706e66658aa3105547f /scripts/basic | |
| parent | 94cea342e8915812b45f93c56e134041c7fdb4d7 (diff) | |
| parent | 564313447e545eea13038f74ada9272ab129b3cb (diff) | |
Merge branch 'revert-advertising-the-tcp-mss-from-the-configured-mtu'
Esko Mobius AKA Yongjian Wang says:
====================
Revert advertising the TCP MSS from the configured MTU
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.
The asymmetric (DSR-style) case that commit targets can still be served
by the existing per-route advmss metric, which overrides the default
after the revert; patch 2 includes a test of that as well. If you would
rather keep the new behaviour as an explicit opt-in some other way, I
am happy to test or rework this.
Patch 1 removes the packetdrill tests that assert the reverted
behaviour, patch 2 is the revert itself.
[1] https://lore.kernel.org/regressions/4F0FAEB6-A13B-47F3-BFF1-C706686C6F64@gmail.com/
====================
Link: https://patch.msgid.link/20261026-advmss-revert-v1-0-272fa4b7ecb6@gmail.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'scripts/basic')
0 files changed, 0 insertions, 0 deletions
