Sagi Grimberg 39d5775746 nvme-tcp: fix timeout handler ... Currently, we have several problems with the timeout handler: 1. If we timeout on the controller establishment flow, we will hang because we don't execute the error recovery (and we shouldn't because the create_ctrl flow needs to fail and cleanup on its own) 2. We might also hang if we get a disconnet on a queue while the controller is already deleting. This racy flow can cause the controller disable/shutdown admin command to hang. We cannot complete a timed out request from the timeout handler without mutual exclusion from the teardown flow (e.g. nvme_rdma_error_recovery_work). So we serialize it in the timeout handler and teardown io and admin queues to guarantee that no one races with us from completing the request. Reviewed-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Sagi Grimberg <sagi@grimberg.me> Signed-off-by: Jens Axboe <axboe@kernel.dk>		2019-01-23 17:16:59 -07:00
..
host	nvme-tcp: fix timeout handler	2019-01-23 17:16:59 -07:00
target	nvmet-tcp: fix uninitialized variable access	2019-01-16 09:44:20 -07:00
Kconfig	nvme: use menu Kconfig interface	2017-10-04 09:43:57 +02:00
Makefile	nvmet: add a generic NVMe target	2016-07-05 11:30:33 -06:00