Sagi Grimberg f1d4ef7d88 nvmet-rdma: register ib_client to not deadlock in device removal ... We can deadlock in case we got to a device removal event on a queue which is already in the process of destroying the cm_id is this is blocking until all events on this cm_id will drain. On the other hand we cannot guarantee that rdma_destroy_id was invoked as we only have indication that the queue disconnect flow has been queued (the queue state is updated before the realease work has been queued). So, we leave all the queue removal to a separate ib_client to avoid this deadlock as ib_client device removal is in a different context than the cm_id itself. Reported-by: Shiraz Saleem <shiraz.saleem@intel.com> Tested-by: Shiraz Saleem <shiraz.saleem@intel.com> Signed-off-by: Sagi Grimberg <sagi@grimberg.me> Signed-off-by: Jens Axboe <axboe@kernel.dk>		2017-06-28 08:14:13 -06:00
..
host	nvme_fc: fix error recovery on link down.	2017-06-28 08:14:13 -06:00
target	nvmet-rdma: register ib_client to not deadlock in device removal	2017-06-28 08:14:13 -06:00
Kconfig	nvmet: add a generic NVMe target	2016-07-05 11:30:33 -06:00
Makefile	nvmet: add a generic NVMe target	2016-07-05 11:30:33 -06:00