Re: [PATCH net-next v12 0/6] tls: receive-path fixes and clean-ups

On Thu, 04 Jun 2026 13:48:23 -0400 Chuck Lever wrote:
> I'd like to encourage in-kernel kTLS consumers (NFSD, NVMe/TCP) to
> coalesce on the use of read_sock. While auditing read_sock for that
> purpose, Hannes and Sabrina flagged a few rough edges in the receive
> paths.
> 
> This series is a set of clean-ups, not a performance series. Async
> batch decryption and its submit/deliver scaffolding were dropped
> during previous review: async_capable is always false for TLS 1.3,
> the version NFSD and NVMe/TCP both require, so async-related
> improvements were unreachable for the in-kernel consumers this
> work targets.
> 
> A subsequent series will introduce infrastructure to support
> KeyUpdate for in-kernel kTLS consumers, which need to handle TLS
> Alert messages that trigger a tlshd upcall.

I still feel like the last patch should have _some_ kind of benchmark /
experimental result included, but okay, let me not torture you :)