[PATCH 12/13] nvme-tcp: reset after recovery for secure concatenation
hare at kernel.org
hare at kernel.org
Sat Jan 27 01:30:57 PST 2024
From: Hannes Reinecke <hare at suse.de>
With TP8018 a new key will be generated from the DH-HMAC-CHAP
protocol after reset or recovery, but we need to start over
to establish a new TLS connection with the new keys.
Signed-off-by: Hannes Reinecke <hare at suse.de>
---
drivers/nvme/host/tcp.c | 42 +++++++++++++++++++++++++++++++++++++++++
1 file changed, 42 insertions(+)
diff --git a/drivers/nvme/host/tcp.c b/drivers/nvme/host/tcp.c
index a46ab8370007..2e504fd9f616 100644
--- a/drivers/nvme/host/tcp.c
+++ b/drivers/nvme/host/tcp.c
@@ -1834,6 +1834,18 @@ static void nvme_tcp_stop_queue(struct nvme_ctrl *nctrl, int qid)
if (test_and_clear_bit(NVME_TCP_Q_LIVE, &queue->flags))
__nvme_tcp_stop_queue(queue);
mutex_unlock(&queue->queue_lock);
+ /*
+ * If the TLS key has not been set
+ * but the queue PSK serial is valid
+ * we are in reset, and should invalidate
+ * the PSK serial for this queue to ensure
+ * TLS won't be started after reset.
+ */
+ if (nvme_tcp_tls_enabled(queue) &&
+ nctrl->opts->concat && !nctrl->opts->tls_key) {
+ dev_dbg(nctrl->device, "queue %d clear TLS PSK\n", qid);
+ queue->tls_key = 0;
+ }
}
static void nvme_tcp_setup_sock_ops(struct nvme_tcp_queue *queue)
@@ -2263,6 +2275,21 @@ static void nvme_tcp_reconnect_ctrl_work(struct work_struct *work)
if (nvme_tcp_setup_ctrl(ctrl, false))
goto requeue;
+ /*
+ * Secure concatenation works in two steps;
+ * the first connection is not encrypted, and
+ * authentication generates the new TLS PSK.
+ * Then the connection needs to be reset,
+ * the TLS needs to be started with the generated
+ * TLS PSK.
+ */
+ if (ctrl->opts->concat && ctrl->opts->tls_key &&
+ !nvme_tcp_tls_enabled(&tcp_ctrl->queues[0])) {
+ dev_info(ctrl->device, "Reset to enable TLS with generated PSK\n");
+ nvme_reset_ctrl(ctrl);
+ return;
+ }
+
dev_info(ctrl->device, "Successfully reconnected (%d attempt)\n",
ctrl->nr_reconnects);
@@ -2284,6 +2311,13 @@ static void nvme_tcp_error_recovery_work(struct work_struct *work)
nvme_stop_keep_alive(ctrl);
flush_work(&ctrl->async_event_work);
+ if (ctrl->opts->concat && ctrl->opts->tls_key) {
+ dev_dbg(ctrl->device, "Wipe generated TLS PSK %0x8\n",
+ key_serial(ctrl->opts->tls_key));
+ key_revoke(ctrl->opts->tls_key);
+ key_put(ctrl->opts->tls_key);
+ ctrl->opts->tls_key = NULL;
+ }
nvme_tcp_teardown_io_queues(ctrl, false);
/* unquiesce to fail fast pending requests */
nvme_unquiesce_io_queues(ctrl);
@@ -2320,6 +2354,14 @@ static void nvme_reset_ctrl_work(struct work_struct *work)
container_of(work, struct nvme_ctrl, reset_work);
nvme_stop_ctrl(ctrl);
+ if (ctrl->opts->concat && ctrl->opts->tls_key &&
+ to_tcp_ctrl(ctrl)->queues[0].tls_key) {
+ dev_dbg(ctrl->device, "Wipe generated TLS PSK %0x8\n",
+ key_serial(ctrl->opts->tls_key));
+ key_revoke(ctrl->opts->tls_key);
+ key_put(ctrl->opts->tls_key);
+ ctrl->opts->tls_key = NULL;
+ }
nvme_tcp_teardown_ctrl(ctrl, false);
if (!nvme_change_ctrl_state(ctrl, NVME_CTRL_CONNECTING)) {
--
2.35.3
More information about the Linux-nvme
mailing list