nvme-auth: update bi_directional flag

While setting chap->s2 to zero as part of secure channel
concatenation, the host missed out to disable the bi_directional
flag to indicate that controller authentication is not requested.
Fix the same.

Fixes: e88a7595b5 ("nvme-tcp: request secure channel concatenation")
Signed-off-by: Martin George <marting@netapp.com>
Reviewed-by: Hannes Reinecke <hare@suse.de>
Signed-off-by: Keith Busch <kbusch@kernel.org>
This commit is contained in:
Martin George
2025-09-15 17:19:21 +05:30
committed by Keith Busch
parent 34585dc649
commit 6ff1bd7846

View File

@@ -331,9 +331,10 @@ static int nvme_auth_set_dhchap_reply_data(struct nvme_ctrl *ctrl,
} else { } else {
memset(chap->c2, 0, chap->hash_len); memset(chap->c2, 0, chap->hash_len);
} }
if (ctrl->opts->concat) if (ctrl->opts->concat) {
chap->s2 = 0; chap->s2 = 0;
else chap->bi_directional = false;
} else
chap->s2 = nvme_auth_get_seqnum(); chap->s2 = nvme_auth_get_seqnum();
data->seqnum = cpu_to_le32(chap->s2); data->seqnum = cpu_to_le32(chap->s2);
if (chap->host_key_len) { if (chap->host_key_len) {