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,
bpf@vger.kernel.org, john.fastabend@gmail.com,
sd@queasysnail.net, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net 0/7] net: tls: fix a few random bugs
Date: Sun, 03 May 2026 02:20:10 +0000 [thread overview]
Message-ID: <177777481080.3993534.13171841772484372879.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260429222944.2139041-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 29 Apr 2026 15:29:37 -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".
>
> Jakub Kicinski (7):
> net: tls: fix silent data drop under pipe back-pressure
> selftests: tls: add test for data loss on small pipe
> net: tls: fix page pin leak on sendpage_ok() failure
> net: tls: fix off-by-one in sg_chain entry count for wrapped sk_msg
> ring
> selftests: bpf: cover wrapped sk_msg ring chaining in ktls TX path
> net: tls: fix use-after-free in tls_sw_sendmsg_locked after bpf
> verdict
> selftests: bpf: cover tls_sw_sendmsg UAF after bpf_exec_tx_verdict
> split
>
> [...]
Here is the summary with links:
- [net,1/7] net: tls: fix silent data drop under pipe back-pressure
https://git.kernel.org/netdev/net/c/7e7be31bfdb0
- [net,2/7] selftests: tls: add test for data loss on small pipe
https://git.kernel.org/netdev/net/c/bd3a4795d574
- [net,3/7] net: tls: fix page pin leak on sendpage_ok() failure
(no matching commit)
- [net,4/7] net: tls: fix off-by-one in sg_chain entry count for wrapped sk_msg ring
(no matching commit)
- [net,5/7] selftests: bpf: cover wrapped sk_msg ring chaining in ktls TX path
(no matching commit)
- [net,6/7] net: tls: fix use-after-free in tls_sw_sendmsg_locked after bpf verdict
(no matching commit)
- [net,7/7] selftests: bpf: cover tls_sw_sendmsg UAF after bpf_exec_tx_verdict split
(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-03 2:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-29 22:29 [PATCH net 0/7] net: tls: fix a few random bugs Jakub Kicinski
2026-04-29 22:29 ` [PATCH net 1/7] net: tls: fix silent data drop under pipe back-pressure Jakub Kicinski
2026-04-29 22:29 ` [PATCH net 2/7] selftests: tls: add test for data loss on small pipe Jakub Kicinski
2026-04-29 22:29 ` [PATCH net 3/7] net: tls: fix page pin leak on sendpage_ok() failure Jakub Kicinski
2026-04-29 22:29 ` [PATCH net 4/7] net: tls: fix off-by-one in sg_chain entry count for wrapped sk_msg ring Jakub Kicinski
2026-05-01 16:40 ` Sabrina Dubroca
2026-05-03 1:26 ` Jakub Kicinski
2026-04-29 22:29 ` [PATCH net 5/7] selftests: bpf: cover wrapped sk_msg ring chaining in ktls TX path Jakub Kicinski
2026-04-30 17:58 ` Jiayuan Chen
2026-04-29 22:29 ` [PATCH net 6/7] net: tls: fix use-after-free in tls_sw_sendmsg_locked after bpf verdict Jakub Kicinski
2026-04-30 17:50 ` Jiayuan Chen
2026-04-29 22:29 ` [PATCH net 7/7] selftests: bpf: cover tls_sw_sendmsg UAF after bpf_exec_tx_verdict split Jakub Kicinski
2026-04-30 17:55 ` Jiayuan Chen
2026-05-03 2:20 ` 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=177777481080.3993534.13171841772484372879.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=linux-kselftest@vger.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