From: Kuniyuki Iwashima <kuniyu@google.com>
To: Yongjian Wang <echoowall@gmail.com>
Cc: pabeni@redhat.com, kuba@kernel.org, shuah@kernel.org,
edumazet@kernel.org, horms@kernel.org, ncardwell@google.com,
davem@davemloft.net, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, netdev@vger.kernel.org,
panweiping3@gmail.com
Subject: Re: [PATCH net-next v4 2/4] selftests/net: packetdrill: test tcp_base_mss on passive connections
Date: Sat, 14 Nov 2026 06:14:50 +0000 [thread overview]
Message-ID: <avf70FWg6nSW1zhX@google.com> (raw)
In-Reply-To: <20261111-mtu-probing-series-v4-2-6f2e484ca8ea@gmail.com>
On Wed, 11 Nov 2026 00:45:56 +0800, Yongjian Wang wrote:
> Check that a passive connection starts at tcp_base_mss with
> net.ipv4.tcp_mtu_probing=2, as an active connection does.
>
> Signed-off-by: Yongjian Wang <echoowall@gmail.com>
Reviewed-by: Kuniyuki Iwashima <kuniyu@google.com>
Somehow this series didn't reach my gmail inbox.
next prev parent reply other threads:[~2026-11-14 6:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 16:45 [PATCH net-next v4 0/4] tcp: fix tcp_base_mss on passive connections and test MTU probing Yongjian Wang
2026-11-10 16:45 ` Yongjian Wang via B4 Relay
2026-11-10 16:45 ` [PATCH net-next v4 1/4] tcp: initialize MTU probing before syncing MSS at connection setup Yongjian Wang
2026-11-10 16:45 ` Yongjian Wang via B4 Relay
2026-11-10 16:45 ` [PATCH net-next v4 2/4] selftests/net: packetdrill: test tcp_base_mss on passive connections Yongjian Wang
2026-11-10 16:45 ` Yongjian Wang via B4 Relay
2026-11-14 6:14 ` Kuniyuki Iwashima [this message]
2026-11-10 16:45 ` [PATCH net-next v4 3/4] selftests/net: packetdrill: add TCP black hole detection tests Yongjian Wang
2026-11-10 16:45 ` Yongjian Wang via B4 Relay
2026-11-14 6:18 ` Kuniyuki Iwashima
2026-11-10 16:45 ` [PATCH net-next v4 4/4] selftests/net: packetdrill: add TCP MTU probing test Yongjian Wang
2026-11-10 16:45 ` Yongjian Wang via B4 Relay
2026-11-14 6:22 ` Kuniyuki Iwashima
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=avf70FWg6nSW1zhX@google.com \
--to=kuniyu@google.com \
--cc=davem@davemloft.net \
--cc=echoowall@gmail.com \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--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 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.