Netdev List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Chuck Lever <cel@kernel.org>
Cc: john.fastabend@gmail.com, kuba@kernel.org, sd@queasysnail.net,
	edumazet@google.com, horms@kernel.org, pabeni@redhat.com,
	netdev@vger.kernel.org, kernel-tls-handshake@lists.linux.dev,
	chuck.lever@oracle.com, sagi@grimberg.me, hare@kernel.org,
	hare@suse.de, alistair.francis@wdc.com
Subject: Re: [PATCH net-next v12 0/6] tls: receive-path fixes and clean-ups
Date: Tue, 09 Jun 2026 03:20:28 +0000	[thread overview]
Message-ID: <178097522813.1776256.11633933878763995491.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260604-tls-read-sock-v12-0-b114efa6e3e2@oracle.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

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



      parent reply	other threads:[~2026-06-09  3:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-04 17:48 [PATCH net-next v12 0/6] tls: receive-path fixes and clean-ups Chuck Lever
2026-06-04 17:48 ` [PATCH net-next v12 1/6] tls: Avoid evaluating freed skb in tls_sw_read_sock() loop Chuck Lever
2026-06-04 17:48 ` [PATCH net-next v12 2/6] tls: Re-present partially-consumed records in tls_sw_read_sock() Chuck Lever
2026-06-04 17:48 ` [PATCH net-next v12 3/6] tls: Move decrypt-failure abort into tls_rx_one_record() Chuck Lever
2026-06-07  3:42   ` Chuck Lever
2026-06-04 17:48 ` [PATCH net-next v12 4/6] tls: Factor tls_strp_msg_consume() from tls_strp_msg_done() Chuck Lever
2026-06-04 17:48 ` [PATCH net-next v12 5/6] tls: Suppress spurious saved_data_ready on all receive paths Chuck Lever
2026-06-04 17:48 ` [PATCH net-next v12 6/6] tls: Flush backlog before waiting for a new record Chuck Lever
2026-06-07 22:10   ` Sabrina Dubroca
2026-06-09  3:11 ` [PATCH net-next v12 0/6] tls: receive-path fixes and clean-ups Jakub Kicinski
2026-06-09  3:20 ` patchwork-bot+netdevbpf [this message]

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=178097522813.1776256.11633933878763995491.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alistair.francis@wdc.com \
    --cc=cel@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=edumazet@google.com \
    --cc=hare@kernel.org \
    --cc=hare@suse.de \
    --cc=horms@kernel.org \
    --cc=john.fastabend@gmail.com \
    --cc=kernel-tls-handshake@lists.linux.dev \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sagi@grimberg.me \
    --cc=sd@queasysnail.net \
    /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