diff options
| author | Chao Leng <lengchao@huawei.com> | 2020-10-12 11:10:40 +0300 |
|---|---|---|
| committer | Christoph Hellwig <hch@lst.de> | 2020-10-22 16:27:13 +0300 |
| commit | 43efdb8e870ee0f58633fd579aa5b5185bf5d39e (patch) | |
| tree | 58d20765edc2c65c0183e425e1ef1a0c6cab4018 /drivers/nvme/host/rdma.c | |
| parent | cb3a92da231bcf55c243d00fa619ee36281b0001 (diff) | |
| download | linux-43efdb8e870ee0f58633fd579aa5b5185bf5d39e.tar.xz | |
nvme-rdma: fix crash when connect rejected
A crash can happened when a connect is rejected. The host establishes
the connection after received ConnectReply, and then continues to send
the fabrics Connect command. If the controller does not receive the
ReadyToUse capsule, host may receive a ConnectReject reply.
Call nvme_rdma_destroy_queue_ib after the host received the
RDMA_CM_EVENT_REJECTED event. Then when the fabrics Connect command
times out, nvme_rdma_timeout calls nvme_rdma_complete_rq to fail the
request. A crash happenes due to use after free in
nvme_rdma_complete_rq.
nvme_rdma_destroy_queue_ib is redundant when handling the
RDMA_CM_EVENT_REJECTED event as nvme_rdma_destroy_queue_ib is already
called in connection failure handler.
Signed-off-by: Chao Leng <lengchao@huawei.com>
Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Diffstat (limited to 'drivers/nvme/host/rdma.c')
| -rw-r--r-- | drivers/nvme/host/rdma.c | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/drivers/nvme/host/rdma.c b/drivers/nvme/host/rdma.c index 9e378d0a0c01..116902b1b2c3 100644 --- a/drivers/nvme/host/rdma.c +++ b/drivers/nvme/host/rdma.c @@ -1926,7 +1926,6 @@ static int nvme_rdma_cm_handler(struct rdma_cm_id *cm_id, complete(&queue->cm_done); return 0; case RDMA_CM_EVENT_REJECTED: - nvme_rdma_destroy_queue_ib(queue); cm_error = nvme_rdma_conn_rejected(queue, ev); break; case RDMA_CM_EVENT_ROUTE_ERROR: |