From: patchwork-bot+netdevbpf@kernel.org
To: Dmitry Safonov <dima@arista.com>
Cc: edumazet@google.com, ncardwell@google.com, kuniyu@google.com,
davem@davemloft.net, dsahern@kernel.org, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, gilligan@arista.com,
noureddine@arista.com, 0x7f454c46@gmail.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v5 0/2] tcp: Destroy TCP-AO, TCP-MD5 keys in .sk_destruct()
Date: Fri, 12 Sep 2025 02:10:22 +0000 [thread overview]
Message-ID: <175764302299.2375845.11338165625021228103.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250909-b4-tcp-ao-md5-rst-finwait2-v5-0-9ffaaaf8b236@arista.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.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
prev parent reply other threads:[~2025-09-12 2:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 1:18 [PATCH net-next v5 0/2] tcp: Destroy TCP-AO, TCP-MD5 keys in .sk_destruct() Dmitry Safonov
2025-09-09 1:18 ` Dmitry Safonov via B4 Relay
2025-09-09 1:18 ` [PATCH net-next v5 1/2] " Dmitry Safonov
2025-09-09 1:18 ` Dmitry Safonov via B4 Relay
2025-09-09 1:18 ` [PATCH net-next v5 2/2] tcp: Free TCP-AO/TCP-MD5 info/keys without RCU Dmitry Safonov
2025-09-09 1:18 ` Dmitry Safonov via B4 Relay
2025-09-12 2:10 ` 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=175764302299.2375845.11338165625021228103.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=0x7f454c46@gmail.com \
--cc=davem@davemloft.net \
--cc=dima@arista.com \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=gilligan@arista.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=noureddine@arista.com \
--cc=pabeni@redhat.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.