From: Matthieu Baerts <matttbe@kernel.org>
To: Eric Dumazet <edumazet@google.com>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Neal Cardwell <ncardwell@google.com>
Cc: Kuniyuki Iwashima <kuniyu@amazon.com>,
Simon Horman <horms@kernel.org>,
netdev@vger.kernel.org, eric.dumazet@gmail.com,
Yong-Hao Zou <yonghaoz1994@gmail.com>
Subject: Re: [PATCH v2 net-next] tcp: be less liberal in TSEcr received while in SYN_RECV state
Date: Tue, 25 Feb 2025 18:31:58 +0100 [thread overview]
Message-ID: <8e05636a-0214-4009-a751-3ed355b5e7f7@kernel.org> (raw)
In-Reply-To: <20250225171048.3105061-1-edumazet@google.com>
Hi Eric,
On 25/02/2025 18:10, Eric Dumazet wrote:
> Yong-Hao Zou mentioned that linux was not strict as other OS in 3WHS,
> for flows using TCP TS option (RFC 7323)
>
> As hinted by an old comment in tcp_check_req(),
> we can check the TSEcr value in the incoming packet corresponds
> to one of the SYNACK TSval values we have sent.
>
> In this patch, I record the oldest and most recent values
> that SYNACK packets have used.
>
> Send a challenge ACK if we receive a TSEcr outside
> of this range, and increase a new SNMP counter.
>
> nstat -az | grep TSEcrRejected
> TcpExtTSEcrRejected 0 0.0
>
> Due to TCP fastopen implementation, do not apply yet these checks
> for fastopen flows.
>
> v2: No longer use req->num_timeout, but treq->snt_tsval_first
> to detect when first SYNACK is prepared. This means
> we make sure to not send an initial zero TSval.
> Make sure MPTCP and TCP selftests are passing.
> Change MIB name to TcpExtTSEcrRejected
Thank you for the v2, and for having ran the MPTCP selftests!
And sorry if my previous replies on the v1 felt like I was rushing you
to send a v2, that was absolutely not my intension!
The v2 looks good to me, just a small detail in the doc. Apart from that:
Reviewed-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
(...)
> diff --git a/Documentation/networking/net_cachelines/snmp.rst b/Documentation/networking/net_cachelines/snmp.rst
> index 90ca2d92547d44fa5b4d28cb9d00820662c3f0fd..bc96efc92cf5b888c1e441412c78f3974be1f587 100644
> --- a/Documentation/networking/net_cachelines/snmp.rst
> +++ b/Documentation/networking/net_cachelines/snmp.rst
> @@ -36,6 +36,7 @@ unsigned_long LINUX_MIB_TIMEWAITRECYCLED
> unsigned_long LINUX_MIB_TIMEWAITKILLED
> unsigned_long LINUX_MIB_PAWSACTIVEREJECTED
> unsigned_long LINUX_MIB_PAWSESTABREJECTED
> +unsigned_long LINUX_MIB_TSECR_REJECTED
Small detail, I guess it should be without the extra underscore:
LINUX_MIB_TSECRREJECTED.
> unsigned_long LINUX_MIB_DELAYEDACKLOST
> unsigned_long LINUX_MIB_LISTENOVERFLOWS
> unsigned_long LINUX_MIB_LISTENDROPS
(...)
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2025-02-25 17:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-25 17:10 [PATCH v2 net-next] tcp: be less liberal in TSEcr received while in SYN_RECV state Eric Dumazet
2025-02-25 17:31 ` Matthieu Baerts [this message]
2025-02-25 20:52 ` Neal Cardwell
2025-02-26 22:47 ` Kuniyuki Iwashima
2025-02-27 3:00 ` patchwork-bot+netdevbpf
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=8e05636a-0214-4009-a751-3ed355b5e7f7@kernel.org \
--to=matttbe@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yonghaoz1994@gmail.com \
/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.