From: patchwork-bot+netdevbpf@kernel.org
To: Sabrina Dubroca <sd@queasysnail.net>
Cc: netdev@vger.kernel.org, vakul.garg@nxp.com, borisp@nvidia.com,
john.fastabend@gmail.com, kuba@kernel.org, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com, horms@kernel.org
Subject: Re: [PATCH net 0/4] tls: a few more fixes for async decrypt
Date: Thu, 29 Feb 2024 17:20:37 +0000 [thread overview]
Message-ID: <170922723735.28034.3350874918349879660.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1709132643.git.sd@queasysnail.net>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 28 Feb 2024 23:43:56 +0100 you wrote:
> The previous patchset [1] took care of "full async". This adds a few
> fixes for cases where only part of the crypto operations go the async
> route, found by extending my previous debug patch [2] to do N
> synchronous operations followed by M asynchronous ops (with N and M
> configurable).
>
> [1] https://patchwork.kernel.org/project/netdevbpf/list/?series=823784&state=*
> [2] https://lore.kernel.org/all/9d664093b1bf7f47497b2c40b3a085b45f3274a2.1694021240.git.sd@queasysnail.net/
>
> [...]
Here is the summary with links:
- [net,1/4] tls: decrement decrypt_pending if no async completion will be called
https://git.kernel.org/netdev/net/c/f7fa16d49837
- [net,2/4] tls: fix peeking with sync+async decryption
https://git.kernel.org/netdev/net/c/6caaf104423d
- [net,3/4] tls: separate no-async decryption request handling from async
https://git.kernel.org/netdev/net/c/41532b785e9d
- [net,4/4] tls: fix use-after-free on failed backlog decryption
https://git.kernel.org/netdev/net/c/13114dc55430
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-02-29 17:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 22:43 [PATCH net 0/4] tls: a few more fixes for async decrypt Sabrina Dubroca
2024-02-28 22:43 ` [PATCH net 1/4] tls: decrement decrypt_pending if no async completion will be called Sabrina Dubroca
2024-02-28 22:43 ` [PATCH net 2/4] tls: fix peeking with sync+async decryption Sabrina Dubroca
2024-02-28 22:43 ` [PATCH net 3/4] tls: separate no-async decryption request handling from async Sabrina Dubroca
2024-02-28 22:44 ` [PATCH net 4/4] tls: fix use-after-free on failed backlog decryption Sabrina Dubroca
2024-02-29 17: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=170922723735.28034.3350874918349879660.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=borisp@nvidia.com \
--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 \
--cc=vakul.garg@nxp.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.