Searched hist:d8f7750a08968b105056328652d2c332bdfa062d (Results 1 – 1 of 1) sorted by relevance
| /openbmc/linux/drivers/nvme/target/ |
| H A D | rdma.c | diff d8f7750a08968b105056328652d2c332bdfa062d Thu May 19 07:24:55 CDT 2016 Sagi Grimberg <sagi@grimberg.me> 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>
|