[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fba600bf-412b-44d5-b2c0-bdf0194bd7e9@redhat.com>
Date: Wed, 31 Dec 2025 10:10:23 +0100
From: Paolo Abeni <pabeni@...hat.com>
To: Rishikesh Jethwani <rjethwani@...estorage.com>, netdev@...r.kernel.org
Cc: saeedm@...dia.com, tariqt@...dia.com, mbloch@...dia.com,
borisp@...dia.com, john.fastabend@...il.com, kuba@...nel.org,
sd@...asysnail.net, davem@...emloft.net
Subject: Re: [PATCH net-next] tls: TLS 1.3 hardware offload support
On 12/30/25 11:41 PM, Rishikesh Jethwani wrote:
> Add TLS 1.3 support to the kernel TLS hardware offload infrastructure,
> enabling hardware acceleration for TLS 1.3 connections on capable NICs.
>
> This patch implements the critical differences between TLS 1.2 and TLS 1.3
> record formats for hardware offload:
>
> TLS 1.2 record structure:
> [Header (5)] + [Explicit IV (8)] + [Ciphertext] + [Tag (16)]
>
> TLS 1.3 record structure:
> [Header (5)] + [Ciphertext + ContentType (1)] + [Tag (16)]
>
> Key changes:
> 1. Content type handling: In TLS 1.3, the content type byte is appended
> to the plaintext before encryption and tag computation. This byte must
> be encrypted along with the ciphertext to compute the correct
> authentication tag. Modified tls_device_record_close() to append
> the content type before the tag for TLS 1.3 records.
>
> 2. Version validation: Both tls_set_device_offload() and
> tls_set_device_offload_rx() now accept TLS_1_3_VERSION in addition
> to TLS_1_2_VERSION.
>
> 3. Pre-populate dummy_page with valid record types for memory
> allocation failure fallback path.
>
> Note: TLS 1.3 protocol parameters (aad_size, tail_size, prepend_size)
> are already handled by init_prot_info() in tls_sw.c.
>
> Testing:
> Verified on Broadcom BCM957608 (Thor 2) and Mellanox ConnectX-6 Dx
> (Crypto Enabled) using ktls_test. Both TX and RX hardware offload working
> successfully with TLS 1.3 AES-GCM-128 and AES-GCM-256 cipher suites.
>
> Signed-off-by: Rishikesh Jethwani <rjethwani@...estorage.com>
## Form letter - net-next-closed
The net-next tree is closed for new drivers, features, code refactoring
and optimizations due to the merge window and the winter break. We are
currently accepting bug fixes only.
Please repost when net-next reopens after Jan 2nd.
RFC patches sent for review only are obviously welcome at any time.
Powered by blists - more mailing lists