From: patchwork-bot+netdevbpf@kernel•org
To: Jakub Kicinski <kuba@kernel•org>
Cc: davem@davemloft•net, pabeni@redhat•com, netdev@vger•kernel.org,
borisp@nvidia•com, john.fastabend@gmail•com,
daniel@iogearbox•net, vfedorenko@novek•ru
Subject: Re: [PATCH net-next 00/10] tls: rx: random refactoring part 3
Date: Wed, 13 Apr 2022 11:00:15 +0000 [thread overview]
Message-ID: <164984761522.32685.5046602676205917906.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220411191917.1240155-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft•net>:
On Mon, 11 Apr 2022 12:19:07 -0700 you wrote:
> TLS Rx refactoring. Part 3 of 3. This set is mostly around rx_list
> and async processing. The last two patches are minor optimizations.
> A couple of features to follow.
>
> Jakub Kicinski (10):
> tls: rx: consistently use unlocked accessors for rx_list
> tls: rx: reuse leave_on_list label for psock
> tls: rx: move counting TlsDecryptErrors for sync
> tls: rx: don't handle TLS 1.3 in the async crypto callback
> tls: rx: assume crypto always calls our callback
> tls: rx: treat process_rx_list() errors as transient
> tls: rx: return the already-copied data on crypto error
> tls: rx: use async as an in-out argument
> tls: rx: use MAX_IV_SIZE for allocations
> tls: rx: only copy IV from the packet for TLS 1.2
>
> [...]
Here is the summary with links:
- [net-next,01/10] tls: rx: consistently use unlocked accessors for rx_list
https://git.kernel.org/netdev/net-next/c/a30295c45472
- [net-next,02/10] tls: rx: reuse leave_on_list label for psock
https://git.kernel.org/netdev/net-next/c/0775639ce1ca
- [net-next,03/10] tls: rx: move counting TlsDecryptErrors for sync
https://git.kernel.org/netdev/net-next/c/284b4d93daee
- [net-next,04/10] tls: rx: don't handle TLS 1.3 in the async crypto callback
https://git.kernel.org/netdev/net-next/c/72f3ad73bc86
- [net-next,05/10] tls: rx: assume crypto always calls our callback
https://git.kernel.org/netdev/net-next/c/1c699ffa48a1
- [net-next,06/10] tls: rx: treat process_rx_list() errors as transient
https://git.kernel.org/netdev/net-next/c/4dcdd971b9c7
- [net-next,07/10] tls: rx: return the already-copied data on crypto error
https://git.kernel.org/netdev/net-next/c/f314bfee81b1
- [net-next,08/10] tls: rx: use async as an in-out argument
https://git.kernel.org/netdev/net-next/c/3547a1f9d988
- [net-next,09/10] tls: rx: use MAX_IV_SIZE for allocations
https://git.kernel.org/netdev/net-next/c/f7d45f4b52fe
- [net-next,10/10] tls: rx: only copy IV from the packet for TLS 1.2
https://git.kernel.org/netdev/net-next/c/a4ae58cdb6e8
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:[~2022-04-13 11:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 19:19 [PATCH net-next 00/10] tls: rx: random refactoring part 3 Jakub Kicinski
2022-04-11 19:19 ` [PATCH net-next 01/10] tls: rx: consistently use unlocked accessors for rx_list Jakub Kicinski
2022-04-11 19:19 ` [PATCH net-next 02/10] tls: rx: reuse leave_on_list label for psock Jakub Kicinski
2022-04-11 19:19 ` [PATCH net-next 03/10] tls: rx: move counting TlsDecryptErrors for sync Jakub Kicinski
2022-04-11 19:19 ` [PATCH net-next 04/10] tls: rx: don't handle TLS 1.3 in the async crypto callback Jakub Kicinski
2022-04-11 19:19 ` [PATCH net-next 05/10] tls: rx: assume crypto always calls our callback Jakub Kicinski
2022-04-11 19:19 ` [PATCH net-next 06/10] tls: rx: treat process_rx_list() errors as transient Jakub Kicinski
2022-04-11 19:19 ` [PATCH net-next 07/10] tls: rx: return the already-copied data on crypto error Jakub Kicinski
2022-04-11 19:19 ` [PATCH net-next 08/10] tls: rx: use async as an in-out argument Jakub Kicinski
2022-04-25 7:19 ` Gal Pressman
2022-04-25 14:54 ` Jakub Kicinski
2022-04-26 6:08 ` Gal Pressman
2022-04-11 19:19 ` [PATCH net-next 09/10] tls: rx: use MAX_IV_SIZE for allocations Jakub Kicinski
2022-04-11 19:19 ` [PATCH net-next 10/10] tls: rx: only copy IV from the packet for TLS 1.2 Jakub Kicinski
2022-04-13 11:00 ` 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=164984761522.32685.5046602676205917906.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=borisp@nvidia$(echo .)com \
--cc=daniel@iogearbox$(echo .)net \
--cc=davem@davemloft$(echo .)net \
--cc=john.fastabend@gmail$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=vfedorenko@novek$(echo .)ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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