From: Sabrina Dubroca <sd@queasysnail.net>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Jiayuan Chen <jiayuan.chen@linux.dev>,
Christopher Lusk <clusk@northecho.dev>,
John Fastabend <john.fastabend@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
netdev@vger.kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH net v3] net: tls: use sync AEAD for sk_msg BPF sockets
Date: Wed, 27 May 2026 10:36:59 +0200 [thread overview]
Message-ID: <ahatK87kXyudML_4@krikkit> (raw)
In-Reply-To: <20260526161101.691d4cb7@kernel.org>
2026-05-26, 16:11:01 -0700, Jakub Kicinski wrote:
> On Tue, 26 May 2026 14:44:24 +0800 Jiayuan Chen wrote:
> > May be time to remove skmsg from ktls? (disable by default first,
> > re-enable via a new ktls module_param?)
>
> Yes, we asked John F off-list to get his attention and I think there's
> only a vague plan to start using kTLS + sockmap, no current user
> (sorry if I misread / misremembered).
That was also what I got from this.
> module params aren't a great API. If we want to deprecate it let's just
> remove the integration in net-next. You have my vote..
+1
and keeping the code around means we still have to maintain it and
deal with the extra complexity.
--
Sabrina
next prev parent reply other threads:[~2026-05-27 8:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 2:51 [PATCH net v3] net: tls: use sync AEAD for sk_msg BPF sockets Christopher Lusk
2026-05-26 6:44 ` Jiayuan Chen
2026-05-26 23:11 ` Jakub Kicinski
2026-05-27 5:09 ` Jiayuan Chen
2026-05-27 19:16 ` John Fastabend
2026-05-27 8:36 ` Sabrina Dubroca [this message]
2026-05-27 12:24 ` Christopher Lusk
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=ahatK87kXyudML_4@krikkit \
--to=sd@queasysnail.net \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=clusk@northecho.dev \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jiayuan.chen@linux.dev \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
/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