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, ycheng@google.com, morleyd@google.com,
netdev@vger.kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH net-next 0/2] tcp: change reaction to ICMP messages
Date: Thu, 16 Nov 2023 23:40:24 +0000 [thread overview]
Message-ID: <170017802483.19305.4105945454875753103.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231114172341.1306769-1-edumazet@google.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Tue, 14 Nov 2023 17:23:39 +0000 you wrote:
> ICMP[v6] messages received for a socket in TCP_SYN_SENT currently abort
> the connection attempt, in violation of standards.
>
> This series changes our stack to adhere to RFC 6069 and RFC 1122 (4.2.3.9)
>
> Eric Dumazet (2):
> tcp: use tp->total_rto to track number of linear timeouts in SYN_SENT
> state
> tcp: no longer abort SYN_SENT when receiving some ICMP
>
> [...]
Here is the summary with links:
- [net-next,1/2] tcp: use tp->total_rto to track number of linear timeouts in SYN_SENT state
https://git.kernel.org/netdev/net-next/c/14dd92d0a117
- [net-next,2/2] tcp: no longer abort SYN_SENT when receiving some ICMP
https://git.kernel.org/netdev/net-next/c/0a8de364ff7a
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:[~2023-11-16 23:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 17:23 [PATCH net-next 0/2] tcp: change reaction to ICMP messages Eric Dumazet
2023-11-14 17:23 ` [PATCH net-next 1/2] tcp: use tp->total_rto to track number of linear timeouts in SYN_SENT state Eric Dumazet
2023-11-14 17:23 ` [PATCH net-next 2/2] tcp: no longer abort SYN_SENT when receiving some ICMP Eric Dumazet
2023-11-16 23:40 ` 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=170017802483.19305.4105945454875753103.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=kuba@kernel.org \
--cc=morleyd@google.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ycheng@google.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.