mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 0/4] tcp: fix tcp_base_mss on passive connections and test MTU probing
Date: Tue, 03 Nov 2026 15:09:40 +0800	[thread overview]
Message-ID: <20261103-mtu-probing-series-v1-0-a2809e725aaa@gmail.com> (raw)

While adding selftests for MTU probing, I noticed that passive
connections do not start at tcp_base_mss with tcp_mtu_probing=2.
Patch 1 fixes that and patch 2 adds a regression test.

This has been wrong since 2014 and only matters with a non-default
sysctl, so I am sending it to net-next. Patch 1 changes behaviour for
users of tcp_mtu_probing=2. Please let me know if you would prefer it
to go through net or to be backported to stable.

Patches 3 and 4 add the missing coverage for black hole detection
(tcp_mtu_probing=1) and for the MTU search on active connections
(tcp_mtu_probing=2).

---
Yongjian Wang (4):
      tcp: sync MSS after enabling MTU probing on passive connections
      selftests/net: packetdrill: test tcp_base_mss on passive connections
      selftests/net: packetdrill: add TCP black hole detection test
      selftests/net: packetdrill: add TCP MTU probing test

 net/ipv4/tcp_input.c                               |  1 +
 .../net/packetdrill/tcp_mtu_probing_blackhole.pkt  | 37 +++++++++++++++++++
 .../net/packetdrill/tcp_mtu_probing_passive.pkt    | 27 ++++++++++++++
 .../net/packetdrill/tcp_mtu_probing_search.pkt     | 43 ++++++++++++++++++++++
 4 files changed, 108 insertions(+)
---
base-commit: 4dd16e31135ea8437a720222df34e8745f385d6d
change-id: 20261103-mtu-probing-series-a87b39fdbedf

Best regards,
--  
Yongjian Wang <echoowall@gmail.com>



             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 Yongjian Wang via B4 Relay [this message]
2026-11-03  7:09 ` [PATCH net-next 1/4] tcp: sync MSS after enabling MTU probing on passive connections Yongjian Wang via B4 Relay
2026-11-07 17:53   ` 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-0-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®