[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<175764302299.2375845.11338165625021228103.git-patchwork-notify@kernel.org>
Date: Fri, 12 Sep 2025 02:10:22 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Dmitry Safonov <dima@...sta.com>
Cc: edumazet@...gle.com, ncardwell@...gle.com, kuniyu@...gle.com,
davem@...emloft.net, dsahern@...nel.org, kuba@...nel.org, pabeni@...hat.com,
horms@...nel.org, gilligan@...sta.com, noureddine@...sta.com,
0x7f454c46@...il.com, netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next v5 0/2] tcp: Destroy TCP-AO, TCP-MD5 keys in
.sk_destruct()
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@...nel.org>:
On Tue, 09 Sep 2025 02:18:49 +0100 you wrote:
> On one side a minor/cosmetic issue, especially nowadays when
> TCP-AO/TCP-MD5 signature verification failures aren't logged to dmesg.
>
> Yet, I think worth addressing for two reasons:
> - unsigned RST gets ignored by the peer and the connection is alive for
> longer (keep-alive interval)
> - netstat counters increase and trace events report that trusted BGP peer
> is sending unsigned/incorrectly signed segments, which can ring alarm
> on monitoring.
>
> [...]
Here is the summary with links:
- [net-next,v5,1/2] tcp: Destroy TCP-AO, TCP-MD5 keys in .sk_destruct()
https://git.kernel.org/netdev/net-next/c/9e472d9e84b1
- [net-next,v5,2/2] tcp: Free TCP-AO/TCP-MD5 info/keys without RCU
https://git.kernel.org/netdev/net-next/c/51e547e8c89c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists