Changpeng Liu de3eb36a61 bdev/nvme: exit controller removal callback if the destruction was started ... For real PCIe drives, if we removed one drive, existing hotplug monitor will trigger the remove callback twice, there is one workaround for vfio-attached device hot remove detection which will also trigger the hot removal callback. For now we add the check in the bdev_nvme layer so that coredump will not happen. Fix issue #606. Change-Id: I0605fbdf391fed20c4aa9a2d54b4f059f29dc483 Signed-off-by: Changpeng Liu <changpeng.liu@intel.com> Reviewed-on: https://review.gerrithub.io/c/445642 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com>		2019-02-22 18:32:17 +00:00
..
bdev_nvme_rpc.c	bdev/nvme: Set per-controller PRCHK options by JSON RPC	2019-02-12 09:14:31 +00:00
bdev_nvme.c	bdev/nvme: exit controller removal callback if the destruction was started	2019-02-22 18:32:17 +00:00
bdev_nvme.h	bdev/nvme: Document prchk flags is not set to hot added NVMe controllers	2019-02-12 09:14:31 +00:00
Makefile	scripts/rpc.py: add method "send_nvme_cmd"	2018-10-22 22:01:14 +00:00
nvme_rpc.c	scripts/rpc.py: add method "send_nvme_cmd"	2018-10-22 22:01:14 +00:00