From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
sd@queasysnail.net, john.fastabend@gmail.com,
bpf@vger.kernel.org
Subject: Re: [PATCH net v2 0/4] net: tls: net: tls: fix a few random bugs
Date: Thu, 14 May 2026 11:30:07 +0000 [thread overview]
Message-ID: <177875820730.4080981.4018205848945747981.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260511174920.433155-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Mon, 11 May 2026 10:49:16 -0700 you wrote:
> Fix a few random bugs, from external reports and my local scan
> with various AI tools. Mostly corner cases in code which I don't
> think TLS maintainers would consider "battle tested".
>
> v2:
> - patches 2 and 3 are new (Sashiko report)
> - patch 4 is rewritten to remove the code instead of fixing it
> - drop the selftests, they were a little too specific, more PoC
> triggers than selftests, and Sashiko kept nit picking
> - old patches 1 and 2 were already applied
> - old patch 3 is gone since it can't trigger today (I will send it
> to net-next)
> v1: https://lore.kernel.org/20260429222944.2139041-1-kuba@kernel.org
>
> [...]
Here is the summary with links:
- [net,v2,1/4] net: tls: fix off-by-one in sg_chain entry count for wrapped sk_msg ring
https://git.kernel.org/netdev/net/c/285943c6e7ca
- [net,v2,2/4] net: tls: prevent chain-after-chain in plain text SG
https://git.kernel.org/netdev/net/c/ff26a0e8377d
- [net,v2,3/4] net: tls: fix use-after-free in tls_sw_sendmsg_locked after bpf verdict
(no matching commit)
- [net,v2,4/4] net: tls: remove bad rollback and UAF on ENOSPC
(no matching commit)
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:[~2026-05-14 11:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 17:49 [PATCH net v2 0/4] net: tls: net: tls: fix a few random bugs Jakub Kicinski
2026-05-11 17:49 ` [PATCH net v2 1/4] net: tls: fix off-by-one in sg_chain entry count for wrapped sk_msg ring Jakub Kicinski
2026-05-12 10:21 ` Sabrina Dubroca
2026-05-11 17:49 ` [PATCH net v2 2/4] net: tls: prevent chain-after-chain in plain text SG Jakub Kicinski
2026-05-12 11:09 ` Sabrina Dubroca
2026-05-12 16:03 ` Jakub Kicinski
2026-05-12 22:30 ` Sabrina Dubroca
2026-05-13 0:14 ` Jakub Kicinski
2026-05-11 17:49 ` [PATCH net v2 3/4] net: tls: fix use-after-free in tls_sw_sendmsg_locked after bpf verdict Jakub Kicinski
2026-05-12 9:47 ` Jiayuan Chen
2026-05-12 16:04 ` Jakub Kicinski
2026-05-11 17:49 ` [PATCH net v2 4/4] net: tls: remove bad rollback and UAF on ENOSPC Jakub Kicinski
2026-05-14 11:18 ` Paolo Abeni
2026-05-14 12:55 ` Sabrina Dubroca
2026-05-14 14:55 ` Jakub Kicinski
2026-05-14 15:05 ` Sabrina Dubroca
2026-05-14 15:09 ` Jakub Kicinski
2026-05-12 9:28 ` [PATCH net v2 0/4] net: tls: net: tls: fix a few random bugs Jakub Sitnicki
2026-05-12 9:37 ` Sabrina Dubroca
2026-05-14 11:30 ` 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=177875820730.4080981.4018205848945747981.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sd@queasysnail.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox