From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
ncardwell@google.com, kuniyu@amazon.com, horms@kernel.org,
netdev@vger.kernel.org, eric.dumazet@gmail.com,
yonghaoz1994@gmail.com, matttbe@kernel.org
Subject: Re: [PATCH v2 net-next] tcp: be less liberal in TSEcr received while in SYN_RECV state
Date: Thu, 27 Feb 2025 03:00:36 +0000 [thread overview]
Message-ID: <174062523624.949564.171648574751933546.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250225171048.3105061-1-edumazet@google.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 25 Feb 2025 17:10:48 +0000 you 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.
>
> [...]
Here is the summary with links:
- [v2,net-next] tcp: be less liberal in TSEcr received while in SYN_RECV state
https://git.kernel.org/netdev/net-next/c/3ba075278c11
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-02-27 3:00 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
2025-02-25 20:52 ` Neal Cardwell
2025-02-26 22:47 ` Kuniyuki Iwashima
2025-02-27 3:00 ` patchwork-bot+netdevbpf [this message]
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=174062523624.949564.171648574751933546.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@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=matttbe@kernel.org \
--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.