diff options
| author | Sagi Grimberg <sagi@grimberg.me> | 2019-04-24 21:53:16 +0300 |
|---|---|---|
| committer | Christoph Hellwig <hch@lst.de> | 2019-04-25 17:51:19 +0300 |
| commit | 569b3d3db1aac8586a16df1745c9e5a99ff47253 (patch) | |
| tree | 851c4f43cf0e49504e011661cf933937efe74c91 | |
| parent | 525ec495e021068aa8635a0e18ff60695f5b1f4f (diff) | |
| download | linux-569b3d3db1aac8586a16df1745c9e5a99ff47253.tar.xz | |
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>
| -rw-r--r-- | drivers/nvme/target/tcp.c | 6 |
1 files changed, 0 insertions, 6 deletions
diff --git a/drivers/nvme/target/tcp.c b/drivers/nvme/target/tcp.c index 17cf137dc88c..69b83fa0c76c 100644 --- 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) { |