nvme-tcp: Fix a C2HTermReq error message

In H2CTermReq, a FES with value 0x05 means "R2T Limit Exceeded"; but
in C2HTermReq the same value has a different meaning (Data Transfer Limit
Exceeded).

Fixes: 84e009042d0f ("nvme-tcp: add basic support for the C2HTermReq PDU")
Signed-off-by: Maurizio Lombardi <mlombard@redhat.com>
Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
Signed-off-by: Keith Busch <kbusch@kernel.org>

diff --git a/drivers/nvme/host/tcp.c b/drivers/nvme/host/tcp.c
index 8c14018201dbde85c49c9ddc099e72cb42bf8bf7..1094cbbec169f3fe37067420006c2e23a18e0910 100644 (file)
--- a/drivers/nvme/host/tcp.c
+++ b/drivers/nvme/host/tcp.c
@@ -775,7 +775,7 @@ static void nvme_tcp_handle_c2h_term(struct nvme_tcp_queue *queue,
                [NVME_TCP_FES_PDU_SEQ_ERR] = "PDU Sequence Error",
                [NVME_TCP_FES_HDR_DIGEST_ERR] = "Header Digest Error",
                [NVME_TCP_FES_DATA_OUT_OF_RANGE] = "Data Transfer Out Of Range",
-               [NVME_TCP_FES_R2T_LIMIT_EXCEEDED] = "R2T Limit Exceeded",
+               [NVME_TCP_FES_DATA_LIMIT_EXCEEDED] = "Data Transfer Limit Exceeded",
                [NVME_TCP_FES_UNSUPPORTED_PARAM] = "Unsupported Parameter",
        };