nvmet-tcp: peek icreq before starting TLS

Browse source

Incoming connection might be either 'normal' NVMe-TCP connections
starting with icreq or TLS handshakes. To ensure that 'normal'
connections can still be handled we need to peek the first packet
and only start TLS handshake if it's not an icreq.
With that we can lift the restriction to always set TREQ to
'required' when TLS1.3 is enabled.

Signed-off-by: Hannes Reinecke <hare@suse.de>
Signed-off-by: Keith Busch <kbusch@kernel.org>

...

This commit is contained in:

Hannes Reinecke 2023-08-24 16:39:25 +02:00 • committed by Keith Busch

parent a1c5dd8355

commit 70525e5d82

3 changed files with 82 additions and 9 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

25

drivers/nvme/target/configfs.c

View file

5

drivers/nvme/target/nvmet.h

View file

61

drivers/nvme/target/tcp.c

View file