From: patchwork-bot+netdevbpf@kernel.org
To: Sabrina Dubroca <sd@queasysnail.net>
Cc: netdev@vger.kernel.org, borisp@nvidia.com,
john.fastabend@gmail.com, kuba@kernel.org, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com
Subject: Re: [PATCH net 0/4] tls: recvmsg fixes
Date: Wed, 27 Mar 2024 04:09:34 +0000 [thread overview]
Message-ID: <171151257431.29046.2588768601360918338.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1711120964.git.sd@queasysnail.net>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 25 Mar 2024 16:56:44 +0100 you wrote:
> The first two fixes are again related to async decrypt. The last one
> is unrelated but I stumbled upon it while reading the code.
>
> Sabrina Dubroca (4):
> tls: recv: process_rx_list shouldn't use an offset with kvec
> tls: adjust recv return with async crypto and failed copy to userspace
> selftests: tls: add test with a partially invalid iov
> tls: get psock ref after taking rxlock to avoid leak
>
> [...]
Here is the summary with links:
- [net,1/4] tls: recv: process_rx_list shouldn't use an offset with kvec
https://git.kernel.org/netdev/net/c/7608a971fdeb
- [net,2/4] tls: adjust recv return with async crypto and failed copy to userspace
https://git.kernel.org/netdev/net/c/85eef9a41d01
- [net,3/4] selftests: tls: add test with a partially invalid iov
https://git.kernel.org/netdev/net/c/dc54b813df63
- [net,4/4] tls: get psock ref after taking rxlock to avoid leak
https://git.kernel.org/netdev/net/c/417e91e85609
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:[~2024-03-27 4:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 15:56 [PATCH net 0/4] tls: recvmsg fixes Sabrina Dubroca
2024-03-25 15:56 ` [PATCH net 1/4] tls: recv: process_rx_list shouldn't use an offset with kvec Sabrina Dubroca
2024-03-26 11:58 ` Simon Horman
2024-03-25 15:56 ` [PATCH net 2/4] tls: adjust recv return with async crypto and failed copy to userspace Sabrina Dubroca
2024-03-26 11:59 ` Simon Horman
2024-03-25 15:56 ` [PATCH net 3/4] selftests: tls: add test with a partially invalid iov Sabrina Dubroca
2024-03-26 11:59 ` Simon Horman
2024-03-25 15:56 ` [PATCH net 4/4] tls: get psock ref after taking rxlock to avoid leak Sabrina Dubroca
2024-03-26 11:59 ` Simon Horman
2024-03-27 4:09 ` 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=171151257431.29046.2588768601360918338.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=borisp@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--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;
as well as URLs for NNTP newsgroup(s).