From: Chuck Lever <cel@kernel.org>
To: Hannes Reinecke <hare@suse.de>, Olga Kornievskaia <okorniev@redhat.com>
Cc: kernel-tls-handshake@lists.linux.dev,
Chuck Lever <chuck.lever@oracle.com>
Subject: [RFC PATCH 0/4] ->read_sock with cmsg
Date: Tue, 17 Feb 2026 17:20:29 -0500 [thread overview]
Message-ID: <20260217222033.1929211-1-cel@kernel.org> (raw)
From: Chuck Lever <chuck.lever@oracle.com>
I'm thinking of proposing this series to netdev to address our
concerns about how in-kernel TLS consumers have to compromise
between efficiency and handling Alerts properly. Posting this series
to a narrow audience for early review.
Based on 26a4cfaff82a2dcb810f6bfd5f4842f9b6046c8a
---
Chuck Lever (4):
net: Introduce read_sock_cmsg proto_ops for control message delivery
tls: Implement read_sock_cmsg for kTLS software path
sunrpc: Use read_sock_cmsg for svcsock TCP receives
sunrpc: Remove sock_recvmsg path from svcsock TCP receives
include/linux/net.h | 8 +
net/sunrpc/svcsock.c | 389 ++++++++++++++++++++-----------------------
net/tls/tls.h | 3 +
net/tls/tls_main.c | 2 +
net/tls/tls_sw.c | 33 +++-
5 files changed, 223 insertions(+), 212 deletions(-)
--
2.53.0
next reply other threads:[~2026-02-17 22:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-17 22:20 Chuck Lever [this message]
2026-02-17 22:20 ` [RFC PATCH 1/4] net: Introduce read_sock_cmsg proto_ops for control message delivery Chuck Lever
2026-02-18 7:29 ` Hannes Reinecke
2026-02-18 14:33 ` Chuck Lever
2026-02-18 15:52 ` Hannes Reinecke
2026-02-18 16:12 ` Chuck Lever
2026-02-19 4:06 ` Alistair Francis
2026-02-19 8:05 ` Hannes Reinecke
2026-02-19 8:10 ` Hannes Reinecke
2026-02-19 13:59 ` Chuck Lever
2026-02-28 11:09 ` Alistair Francis
2026-02-17 22:20 ` [RFC PATCH 2/4] tls: Implement read_sock_cmsg for kTLS software path Chuck Lever
2026-02-17 22:20 ` [RFC PATCH 3/4] sunrpc: Use read_sock_cmsg for svcsock TCP receives Chuck Lever
2026-02-17 22:20 ` [RFC PATCH 4/4] sunrpc: Remove sock_recvmsg path from " Chuck Lever
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=20260217222033.1929211-1-cel@kernel.org \
--to=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=hare@suse.de \
--cc=kernel-tls-handshake@lists.linux.dev \
--cc=okorniev@redhat.com \
/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