From: Sabrina Dubroca <sd@queasysnail.net>
To: netdev@vger.kernel.org
Cc: borisp@nvidia.com, john.fastabend@gmail.com, kuba@kernel.org,
Sabrina Dubroca <sd@queasysnail.net>,
"Gustavo A . R . Silva" <gustavoars@kernel.org>
Subject: [PATCH net-next 00/14] net: tls: various code cleanups and improvements
Date: Mon, 9 Oct 2023 22:50:40 +0200 [thread overview]
Message-ID: <cover.1696596130.git.sd@queasysnail.net> (raw)
This series contains multiple cleanups and simplifications for the
config code of both TLS_SW and TLS_HW.
It also modifies the chcr_ktls driver to use driver_state like all
other drivers, so that we can then make driver_state fixed size
instead of a flex array always allocated to that same fixed size. As
reported by Gustavo A. R. Silva, the way chcr_ktls misuses
driver_state irritates GCC [1].
Patches 1 and 2 are follow-ups to my previous cipher_desc series.
[1] https://lore.kernel.org/netdev/ZRvzdlvlbX4+eIln@work/
Sabrina Dubroca (14):
tls: get salt using crypto_info_salt in tls_enc_skb
tls: drop unnecessary cipher_type checks in tls offload
tls: store rec_seq directly within cipher_context
tls: rename MAX_IV_SIZE to TLS_MAX_IV_SIZE
tls: store iv directly within cipher_context
tls: extract context alloc/initialization out of tls_set_sw_offload
tls: move tls_prot_info initialization out of tls_set_sw_offload
tls: also use init_prot_info in tls_set_device_offload
tls: add a helper to allocate/initialize offload_ctx_tx
tls: remove tls_context argument from tls_set_sw_offload
tls: remove tls_context argument from tls_set_device_offload
tls: validate crypto_info in a separate helper
chcr_ktls: use tls_offload_context_tx and driver_state like other
drivers
tls: use fixed size for tls_offload_context_{tx,rx}.driver_state
.../chelsio/inline_crypto/ch_ktls/chcr_ktls.c | 43 ++--
.../chelsio/inline_crypto/ch_ktls/chcr_ktls.h | 36 +++-
include/net/tls.h | 21 +-
net/tls/tls.h | 12 +-
net/tls/tls_device.c | 101 ++++-----
net/tls/tls_device_fallback.c | 23 +-
net/tls/tls_main.c | 62 +++---
net/tls/tls_sw.c | 198 +++++++++---------
8 files changed, 244 insertions(+), 252 deletions(-)
--
2.42.0
next reply other threads:[~2023-10-09 20:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 20:50 Sabrina Dubroca [this message]
2023-10-09 20:50 ` [PATCH net-next 01/14] tls: get salt using crypto_info_salt in tls_enc_skb Sabrina Dubroca
2023-10-09 20:50 ` [PATCH net-next 02/14] tls: drop unnecessary cipher_type checks in tls offload Sabrina Dubroca
2023-10-09 20:50 ` [PATCH net-next 03/14] tls: store rec_seq directly within cipher_context Sabrina Dubroca
2023-10-09 20:50 ` [PATCH net-next 04/14] tls: rename MAX_IV_SIZE to TLS_MAX_IV_SIZE Sabrina Dubroca
2023-10-09 20:50 ` [PATCH net-next 05/14] tls: store iv directly within cipher_context Sabrina Dubroca
2023-10-09 20:50 ` [PATCH net-next 06/14] tls: extract context alloc/initialization out of tls_set_sw_offload Sabrina Dubroca
2023-10-09 20:50 ` [PATCH net-next 07/14] tls: move tls_prot_info initialization " Sabrina Dubroca
2023-10-09 20:50 ` [PATCH net-next 08/14] tls: also use init_prot_info in tls_set_device_offload Sabrina Dubroca
2023-10-13 21:23 ` Jakub Kicinski
2023-10-17 9:16 ` Sabrina Dubroca
2023-10-17 7:08 ` Tariq Toukan
2023-10-09 20:50 ` [PATCH net-next 09/14] tls: add a helper to allocate/initialize offload_ctx_tx Sabrina Dubroca
2023-10-09 20:50 ` [PATCH net-next 10/14] tls: remove tls_context argument from tls_set_sw_offload Sabrina Dubroca
2023-10-09 20:50 ` [PATCH net-next 11/14] tls: remove tls_context argument from tls_set_device_offload Sabrina Dubroca
2023-10-09 20:50 ` [PATCH net-next 12/14] tls: validate crypto_info in a separate helper Sabrina Dubroca
2023-10-09 20:50 ` [PATCH net-next 13/14] chcr_ktls: use tls_offload_context_tx and driver_state like other drivers Sabrina Dubroca
2023-10-09 20:50 ` [PATCH net-next 14/14] tls: use fixed size for tls_offload_context_{tx,rx}.driver_state Sabrina Dubroca
2023-10-13 9:47 ` [PATCH net-next 00/14] net: tls: various code cleanups and improvements Simon Horman
2023-10-13 10:30 ` patchwork-bot+netdevbpf
2023-10-13 21:23 ` Jakub Kicinski
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=cover.1696596130.git.sd@queasysnail.net \
--to=sd@queasysnail.net \
--cc=borisp@nvidia.com \
--cc=gustavoars@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
/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).