[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230703090444.38734-1-hare@suse.de>
Date: Mon, 3 Jul 2023 11:04:39 +0200
From: Hannes Reinecke <hare@...e.de>
To: Sagi Grimberg <sagi@...mberg.me>
Cc: Keith Busch <kbusch@...nel.org>,
Christoph Hellwig <hch@....de>,
linux-nvme@...ts.infradead.org,
Jakub Kicinski <kuba@...nel.org>,
Eric Dumazet <edumazet@...gle.com>,
Paolo Abeni <pabeni@...hat.com>,
netdev@...r.kernel.org,
Hannes Reinecke <hare@...e.de>
Subject: [PATCHv6 0/5] net/tls: fixes for NVMe-over-TLS
Hi all,
here are some small fixes to get NVMe-over-TLS up and running.
The first three are just minor modifications to have MSG_EOR handled
for TLS (and adding a test for it), but the last two implement the
->read_sock() callback for tls_sw and that, I guess, could do with
some reviews.
It does work with my NVMe-TLS test harness, but what do I know :-)
As usual, comments and reviews are welcome.
Changes to the original submission:
- Add a testcase for MSG_EOR handling
Changes to v2:
- Bail out on conflicting message flags
- Rework flag handling
Changes to v3:
- Return -EINVAL on conflicting flags
- Rebase on top of net-next
Changes to v4:
- Add tlx_rx_reader_lock() to read_sock
- Add MSG_EOR handling to tls_sw_readpages()
Changes to v5:
- Rebase to latest upstream
- Split tls_rx_reader_lock() as suggested by Sagi
Hannes Reinecke (5):
net/tls: handle MSG_EOR for tls_sw TX flow
net/tls: handle MSG_EOR for tls_device TX flow
selftests/net/tls: add test for MSG_EOR
net/tls: split tls_rx_reader_lock
net/tls: implement ->read_sock()
net/tls/tls.h | 2 +
net/tls/tls_device.c | 6 +-
net/tls/tls_main.c | 2 +
net/tls/tls_sw.c | 121 +++++++++++++++++++++++++-----
tools/testing/selftests/net/tls.c | 11 +++
5 files changed, 124 insertions(+), 18 deletions(-)
--
2.35.3
Powered by blists - more mailing lists