linux_dsm_epyc7002/drivers/nvme
Sagi Grimberg d8f7750a08 nvmet-rdma: Correctly handle RDMA device hot removal
When configuring a device attached listener, we may
see device removal events. In this case we return a
non-zero return code from the cm event handler which
implicitly destroys the cm_id. It is possible that in
the future the user will remove this listener and by
that trigger a second call to rdma_destroy_id on an
already destroyed cm_id -> BUG.

In addition, when a queue bound (active session) cm_id
generates a DEVICE_REMOVAL event we must guarantee all
resources are cleaned up by the time we return from the
event handler.

Introduce nvmet_rdma_device_removal which addresses
(or at least attempts to) both scenarios.

Signed-off-by: Sagi Grimberg <sagi@grimberg.me>
Reviewed-by: Christoph Hellwig <hch@lst.de>
2016-08-04 17:43:06 +03:00
..
host nvme-rdma: Make sure to shutdown the controller if we can 2016-08-03 16:25:23 +03:00
target nvmet-rdma: Correctly handle RDMA device hot removal 2016-08-04 17:43:06 +03: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