nvmet-tcp: don't fail maxr2t greater than 1

The host may support it, but nothing prevents us from
sending a single r2t at a time like we do anyways.

Signed-off-by: Sagi Grimberg <sagi@grimberg.me>
Signed-off-by: Christoph Hellwig <hch@lst.de>

diff --git a/drivers/nvme/target/tcp.c b/drivers/nvme/target/tcp.c
index 17cf137dc88c4f2973f8b335e4fe40954edd9282..69b83fa0c76c173ed040d4ea9a0e9db3551582d0 100644 (file)
--- a/drivers/nvme/target/tcp.c
+++ b/drivers/nvme/target/tcp.c
@@ -774,12 +774,6 @@ static int nvmet_tcp_handle_icreq(struct nvmet_tcp_queue *queue)
                return -EPROTO;
        }
 
-       if (icreq->maxr2t != 0) {
-               pr_err("queue %d: unsupported maxr2t %d\n", queue->idx,
-                       le32_to_cpu(icreq->maxr2t) + 1);
-               return -EPROTO;
-       }
-
        queue->hdr_digest = !!(icreq->digest & NVME_TCP_HDR_DIGEST_ENABLE);
        queue->data_digest = !!(icreq->digest & NVME_TCP_DATA_DIGEST_ENABLE);
        if (queue->hdr_digest || queue->data_digest) {