Re: [PATCH net-next v2 3/6] tls: Implement read_sock_rectype for kTLS software path

On 7/20/26 4:27 PM, Chuck Lever wrote:
> From: Chuck Lever <[email protected]>
> 
> tls_sw_read_sock() rejects non-data records (alerts, handshake
> messages) with -EINVAL. Kernel consumers that need TLS alert
> delivery, such as NFSD, NFS client, and NVMe target, must fall back
> to the sock_recvmsg() API to receive control messages via CMSG.
> 
> Implement the new read_sock_rectype() method for these consumers,
> delivering non-data records to a callback through the kTLS software
> receive path.
> 
> Signed-off-by: Chuck Lever <[email protected]>
> ---
>   net/tls/tls.h      |  3 +++
>   net/tls/tls_main.c |  5 +++++
>   net/tls/tls_sw.c   | 41 ++++++++++++++++++++++++++++++++++++-----
>   3 files changed, 44 insertions(+), 5 deletions(-)
> 
Reviewed-by: Hannes Reinecke <[email protected]>

Cheers,

Hannes
-- 
Dr. Hannes Reinecke                  Kernel Storage Architect
[email protected]                                +49 911 74053 688
SUSE Software Solutions GmbH, Frankenstr. 146, 90461 Nürnberg
HRB 36809 (AG Nürnberg), GF: I. Totev, A. McDonald, W. Knoblich