Re: [PATCH net-next v12 0/6] tls: receive-path fixes and clean-ups
[email protected] Tue, 09 Jun 2026 03:20:28 +0000
| Newsgroups | dev.linux.lists.kernel-tls-handshake,org.kernel.vger.netdev |
|---|---|
| Message-ID | <178097522813.1776256.11633933878763995491.git-patchwork-notify@kernel.org> |
Hello: This series was applied to netdev/net-next.git (main) by Jakub Kicinski <[email protected]>: On Thu, 04 Jun 2026 13:48:23 -0400 you 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. > > [...] Here is the summary with links: - [net-next,v12,1/6] tls: Avoid evaluating freed skb in tls_sw_read_sock() loop https://git.kernel.org/netdev/net-next/c/4da7925c124a - [net-next,v12,2/6] tls: Re-present partially-consumed records in tls_sw_read_sock() https://git.kernel.org/netdev/net-next/c/3f05d3bf9422 - [net-next,v12,3/6] tls: Move decrypt-failure abort into tls_rx_one_record() https://git.kernel.org/netdev/net-next/c/524bc67509ff - [net-next,v12,4/6] tls: Factor tls_strp_msg_consume() from tls_strp_msg_done() https://git.kernel.org/netdev/net-next/c/8cf0c70ec84d - [net-next,v12,5/6] tls: Suppress spurious saved_data_ready on all receive paths https://git.kernel.org/netdev/net-next/c/22f8bf8808dc - [net-next,v12,6/6] tls: Flush backlog before waiting for a new record https://git.kernel.org/netdev/net-next/c/edcf32b8a48f You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html