From: Jakub Kicinski <kuba@kernel.org>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: Hannes Reinecke <hare@suse.de>, Christoph Hellwig <hch@lst.de>,
Keith Busch <kbusch@kernel.org>,
linux-nvme@lists.infradead.org,
Chuck Lever <chuck.lever@oracle.com>,
kernel-tls-handshake@lists.linux.dev,
Boris Pismenny <boris.pismenny@gmail.com>
Subject: Re: [PATCH 06/17] net/tls: implement ->read_sock()
Date: Tue, 9 May 2023 17:47:24 -0700 [thread overview]
Message-ID: <20230509174724.4a198306@kernel.org> (raw)
In-Reply-To: <da7135cf-c96e-f79f-9d49-87ee269871cf@grimberg.me>
On Tue, 9 May 2023 16:30:03 -0700 Sagi Grimberg wrote:
> Can we get an ack (or review) from you on this?
>
> The only consumer of this is nvme, and seems to at least
> work on the limited testing this series has seen.
>
> We can take this piece from the nvme tree or not, whatever
> you prefer.
Let's get all the TLS patches posted to netdev, reviewed there,
then we can put them on a branch on top of -rc1 and they can
be pulled into both netdev and nvme tree.
next prev parent reply other threads:[~2023-05-10 0:47 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 6:56 [PATCHv4 00/17] nvme: In-kernel TLS support for TCP Hannes Reinecke
2023-04-19 6:56 ` [PATCH 01/17] nvme-keyring: register '.nvme' keyring Hannes Reinecke
2023-05-02 14:17 ` Aurelien Aptel
2023-04-19 6:56 ` [PATCH 02/17] nvme-keyring: define a 'psk' keytype Hannes Reinecke
2023-05-08 8:59 ` Max Gurtovoy
2023-05-08 13:56 ` Hannes Reinecke
2023-04-19 6:57 ` [PATCH 03/17] nvme: add TCP TSAS definitions Hannes Reinecke
2023-05-08 16:36 ` Max Gurtovoy
2023-05-08 21:01 ` Hannes Reinecke
2023-04-19 6:57 ` [PATCH 04/17] nvme-tcp: add definitions for TLS cipher suites Hannes Reinecke
2023-04-19 6:57 ` [PATCH 05/17] nvme-keyring: implement nvme_tls_psk_default() Hannes Reinecke
2023-05-09 7:31 ` Max Gurtovoy
2023-05-09 14:13 ` Hannes Reinecke
2023-04-19 6:57 ` [PATCH 06/17] net/tls: implement ->read_sock() Hannes Reinecke
2023-04-19 9:09 ` Sagi Grimberg
2023-05-09 23:30 ` Sagi Grimberg
2023-05-10 0:47 ` Jakub Kicinski [this message]
2023-05-17 6:43 ` Sagi Grimberg
2023-05-17 7:53 ` Hannes Reinecke
2023-05-17 7:54 ` Christoph Hellwig
2023-05-17 7:56 ` Hannes Reinecke
2023-05-17 9:36 ` Sagi Grimberg
2023-04-19 6:57 ` [PATCH 07/17] net/tls: handle MSG_EOR for tls_sw TX flow Hannes Reinecke
2023-05-09 9:19 ` Max Gurtovoy
2023-05-09 14:18 ` Hannes Reinecke
2023-05-09 15:13 ` Jakub Kicinski
2023-05-09 23:02 ` Max Gurtovoy
2023-05-09 23:07 ` Hannes Reinecke
2023-04-19 6:57 ` [PATCH 08/17] nvme-tcp: fixup MSG_SENDPAGE_NOTLAST Hannes Reinecke
2023-04-19 9:08 ` Sagi Grimberg
2023-04-19 6:57 ` [PATCH 09/17] security/keys: export key_lookup() Hannes Reinecke
2023-04-19 6:57 ` [PATCH 10/17] nvme/tcp: allocate socket file Hannes Reinecke
2023-04-19 6:57 ` [PATCH 11/17] nvme-tcp: enable TLS handshake upcall Hannes Reinecke
2023-05-09 9:48 ` Max Gurtovoy
2023-05-09 14:22 ` Hannes Reinecke
2023-05-09 23:16 ` Max Gurtovoy
2023-05-10 7:37 ` Hannes Reinecke
2023-05-10 16:26 ` Daniel Wagner
2023-04-19 6:57 ` [PATCH 12/17] nvme-tcp: control message handling for recvmsg() Hannes Reinecke
2023-04-19 6:57 ` [PATCH 13/17] nvme-fabrics: parse options 'keyring' and 'tls_key' Hannes Reinecke
2023-04-21 6:32 ` Daniel Wagner
2023-05-09 10:00 ` Max Gurtovoy
2023-05-09 14:24 ` Hannes Reinecke
2023-04-19 6:57 ` [PATCH 14/17] nvmet: make TCP sectype settable via configfs Hannes Reinecke
2023-04-19 6:57 ` [PATCH 15/17] nvmet-tcp: allocate socket file Hannes Reinecke
2023-04-19 6:57 ` [PATCH 16/17] nvmet-tcp: enable TLS handshake upcall Hannes Reinecke
2023-04-19 6:57 ` [PATCH 17/17] nvmet-tcp: control messages for recvmsg() 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=20230509174724.4a198306@kernel.org \
--to=kuba@kernel.org \
--cc=boris.pismenny@gmail.com \
--cc=chuck.lever@oracle.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=kernel-tls-handshake@lists.linux.dev \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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.