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>
This commit is contained in:
parent
525ec495e0
commit
569b3d3db1
|
@ -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) {
|
||||
|
|
Loading…
Reference in New Issue
Block a user