From: Jakub Kicinski <kuba@kernel.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: pabeni@redhat.com, edumazet@google.com, netdev@vger.kernel.org,
hare@suse.com, dhowells@redhat.com, bcodding@redhat.com,
kolga@netapp.com, jmeneghi@redhat.com
Subject: Re: [PATCH v3 1/2] net/handshake: Create a NETLINK service for handling handshake requests
Date: Wed, 8 Feb 2023 22:00:25 -0800 [thread overview]
Message-ID: <20230208220025.0c3e6591@kernel.org> (raw)
In-Reply-To: <167580607317.5328.2575913180270613320.stgit@91.116.238.104.host.secureserver.net>
On Tue, 07 Feb 2023 16:41:13 -0500 Chuck Lever wrote:
> diff --git a/tools/include/uapi/linux/netlink.h b/tools/include/uapi/linux/netlink.h
> index 0a4d73317759..a269d356f358 100644
> --- a/tools/include/uapi/linux/netlink.h
> +++ b/tools/include/uapi/linux/netlink.h
> @@ -29,6 +29,7 @@
> #define NETLINK_RDMA 20
> #define NETLINK_CRYPTO 21 /* Crypto layer */
> #define NETLINK_SMC 22 /* SMC monitoring */
> +#define NETLINK_HANDSHAKE 23 /* transport layer sec handshake requests */
The extra indirection of genetlink introduces some complications?
next prev parent reply other threads:[~2023-02-09 6:00 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 21:41 [PATCH v3 0/2] Another crack at a handshake upcall mechanism Chuck Lever
2023-02-07 21:41 ` [PATCH v3 1/2] net/handshake: Create a NETLINK service for handling handshake requests Chuck Lever
2023-02-08 16:20 ` Hannes Reinecke
2023-02-09 6:00 ` Jakub Kicinski [this message]
2023-02-09 15:43 ` Chuck Lever III
2023-02-09 16:02 ` Paolo Abeni
2023-02-09 16:34 ` Chuck Lever III
2023-02-10 11:41 ` Paolo Abeni
2023-02-10 14:31 ` Chuck Lever III
2023-02-10 15:06 ` Hannes Reinecke
2023-02-10 15:21 ` Paolo Abeni
2023-02-10 15:38 ` Chuck Lever III
2023-02-12 15:40 ` Jamal Hadi Salim
2023-02-12 17:24 ` Chuck Lever III
2023-02-10 2:07 ` Jakub Kicinski
2023-02-10 14:17 ` Chuck Lever III
2023-02-10 18:09 ` Jakub Kicinski
2023-02-10 19:04 ` Chuck Lever III
2023-02-10 21:44 ` Jakub Kicinski
2023-02-11 20:55 ` Chuck Lever III
2023-02-13 21:40 ` Jakub Kicinski
2023-02-11 12:11 ` Hannes Reinecke
2023-02-13 21:55 ` Jakub Kicinski
2023-02-07 21:41 ` [PATCH v3 2/2] net/tls: Support AF_HANDSHAKE in kTLS Chuck Lever
2023-02-08 16:34 ` Hannes Reinecke
2023-02-08 17:04 ` Chuck Lever III
2023-02-08 17:48 ` Marcel Holtmann
2023-02-14 9:44 ` [PATCH v3 0/2] Another crack at a handshake upcall mechanism Hannes Reinecke
2023-02-14 11:09 ` Hannes Reinecke
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=20230208220025.0c3e6591@kernel.org \
--to=kuba@kernel.org \
--cc=bcodding@redhat.com \
--cc=chuck.lever@oracle.com \
--cc=dhowells@redhat.com \
--cc=edumazet@google.com \
--cc=hare@suse.com \
--cc=jmeneghi@redhat.com \
--cc=kolga@netapp.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@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 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.