From: Jakub Kicinski <kuba@kernel.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: netdev@vger.kernel.org, hare@suse.com, dhowells@redhat.com,
kolga@netapp.com, jmeneghi@redhat.com, bcodding@redhat.com,
jlayton@redhat.com
Subject: Re: [PATCH v2 2/3] net/handshake: Add support for PF_HANDSHAKE
Date: Sat, 28 Jan 2023 00:32:12 -0800 [thread overview]
Message-ID: <20230128003212.7f37b45c@kernel.org> (raw)
In-Reply-To: <167474894272.5189.9499312703868893688.stgit@91.116.238.104.host.secureserver.net>
On Thu, 26 Jan 2023 11:02:22 -0500 Chuck Lever wrote:
> I've designed a way to pass a connected kernel socket endpoint to
> user space using the traditional listen/accept mechanism. accept(2)
> gives us a well-worn building block that can materialize a connected
> socket endpoint as a file descriptor in a specific user space
> process. Like any open socket descriptor, the accepted FD can then
> be passed to a library such as GnuTLS to perform a TLS handshake.
I can't bring myself to like the new socket family layer.
I'd like a second opinion on that, if anyone within netdev
is willing to share..
next prev parent reply other threads:[~2023-01-28 8:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 16:02 [PATCH v2 0/3] Another crack at a handshake upcall mechanism Chuck Lever
2023-01-26 16:02 ` [PATCH v2 1/3] net: Add an AF_HANDSHAKE address family Chuck Lever
2023-01-26 16:02 ` [PATCH v2 2/3] net/handshake: Add support for PF_HANDSHAKE Chuck Lever
2023-01-28 8:32 ` Jakub Kicinski [this message]
2023-01-28 14:06 ` Chuck Lever III
2023-01-31 4:35 ` Jakub Kicinski
2023-01-31 15:18 ` Chuck Lever III
2023-01-31 19:30 ` Jakub Kicinski
2023-01-31 19:34 ` Chuck Lever III
2023-01-31 20:23 ` Marcel Holtmann
2023-01-31 20:26 ` Benjamin Coddington
2023-01-28 17:40 ` Stephen Hemminger
2023-01-29 16:53 ` Chuck Lever III
2023-01-29 16:21 ` Hannes Reinecke
2023-01-30 13:44 ` Marcel Holtmann
2023-01-30 15:00 ` Chuck Lever III
2023-01-31 7:40 ` Hannes Reinecke
2023-01-31 14:17 ` Marcel Holtmann
2023-01-31 14:47 ` Hannes Reinecke
2023-01-31 20:32 ` Marcel Holtmann
2023-02-01 7:09 ` Hannes Reinecke
2023-02-02 17:13 ` Xin Long
2023-02-02 17:32 ` Hannes Reinecke
2023-01-26 16:02 ` [PATCH v2 3/3] net/tls: Support AF_HANDSHAKE in kTLS 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=20230128003212.7f37b45c@kernel.org \
--to=kuba@kernel.org \
--cc=bcodding@redhat.com \
--cc=chuck.lever@oracle.com \
--cc=dhowells@redhat.com \
--cc=hare@suse.com \
--cc=jlayton@redhat.com \
--cc=jmeneghi@redhat.com \
--cc=kolga@netapp.com \
--cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.