From: Yongjian Wang via B4 Relay <devnull+echoowall.gmail.com@kernel.org>
To: ncardwell@google.com, horms@kernel.org, edumazet@kernel.org,
kuba@kernel.org, kuniyu@google.com, shuah@kernel.org,
davem@davemloft.net, pabeni@redhat.com
Cc: netdev@vger.kernel.org, panweiping3@gmail.com,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
Yongjian Wang <echoowall@gmail.com>
Subject: [PATCH net-next 1/4] tcp: sync MSS after enabling MTU probing on passive connections
Date: Tue, 03 Nov 2026 15:09:41 +0800 [thread overview]
Message-ID: <20261103-mtu-probing-series-v1-1-a2809e725aaa@gmail.com> (raw)
In-Reply-To: <20261103-mtu-probing-series-v1-0-a2809e725aaa@gmail.com>
From: Yongjian Wang <echoowall@gmail.com>
tcp_v4_syn_recv_sock() and tcp_v6_syn_recv_sock() call tcp_sync_mss()
before MTU probing is enabled, and tcp_init_transfer() enables it later
without syncing the MSS again.
With net.ipv4.tcp_mtu_probing=2, a passive connection therefore starts
at the full MSS instead of tcp_base_mss as documented, while an active
connection starts at tcp_base_mss. This has two visible effects, shown
here with tcp_base_mss=1024:
- The MSS drops when the first probe is acknowledged, from 1460 to 1242,
although that probe has just shown the path can carry more.
- On a black hole path the MSS never tries tcp_base_mss. It goes from
1460 straight to 512, since MTU probing is already enabled when black
hole detection triggers.
Sync the MSS right after tcp_mtup_init(). tcp_sync_mss() only applies
search_low when MTU probing is enabled, so the other tcp_mtu_probing
values keep their behaviour.
The Fixes commit kept tcp_mtup_init() in a single place on purpose, so
sync the MSS next to it instead of moving it back into the
syn_recv_sock() handlers.
Fixes: 4d83e1773031 ("tcp: delete redundant calls of tcp_mtup_init()")
Signed-off-by: Yongjian Wang <echoowall@gmail.com>
---
net/ipv4/tcp_input.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/net/ipv4/tcp_input.c b/net/ipv4/tcp_input.c
index e1f2d9765..c13f005b2 100644
--- a/net/ipv4/tcp_input.c
+++ b/net/ipv4/tcp_input.c
@@ -6760,6 +6760,7 @@ void tcp_init_transfer(struct sock *sk, int bpf_op, struct sk_buff *skb)
struct tcp_sock *tp = tcp_sk(sk);
tcp_mtup_init(sk);
+ tcp_sync_mss(sk, icsk->icsk_pmtu_cookie);
icsk->icsk_af_ops->rebuild_header(sk);
tcp_init_metrics(sk);
--
Git-157)
next prev parent reply other threads:[~2026-11-03 7:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 7:09 [PATCH net-next 0/4] tcp: fix tcp_base_mss on passive connections and test MTU probing Yongjian Wang via B4 Relay
2026-11-03 7:09 ` Yongjian Wang via B4 Relay [this message]
2026-11-07 17:53 ` [PATCH net-next 1/4] tcp: sync MSS after enabling MTU probing on passive connections Neal Cardwell
2026-11-07 19:15 ` Kuniyuki Iwashima
2026-11-03 7:09 ` [PATCH net-next 2/4] selftests/net: packetdrill: test tcp_base_mss " Yongjian Wang via B4 Relay
2026-11-03 7:09 ` [PATCH net-next 3/4] selftests/net: packetdrill: add TCP black hole detection test Yongjian Wang via B4 Relay
2026-11-03 7:09 ` [PATCH net-next 4/4] selftests/net: packetdrill: add TCP MTU probing test Yongjian Wang via B4 Relay
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=20261103-mtu-probing-series-v1-1-a2809e725aaa@gmail.com \
--to=devnull+echoowall.gmail.com@kernel.org \
--cc=davem@davemloft.net \
--cc=echoowall@gmail.com \
--cc=edumazet@kernel.org \
--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=panweiping3@gmail.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
all inboxes | Powered by JetHome®