summaryrefslogtreecommitdiffstats
path: root/drivers/nvme/target/discovery.c
diff options
context:
space:
mode:
authorMing Lei <ming.lei@redhat.com>2017-11-09 12:32:07 +0100
committerJens Axboe <axboe@kernel.dk>2017-11-11 03:53:25 +0100
commit03e0f3a65e4da497c3b7b213c68943cbc73a2e34 (patch)
tree0eff01e06d1998f467cfff23abaebba9316b77c6 /drivers/nvme/target/discovery.c
parentnvme: send uevent for some asynchronous events (diff)
downloadlinux-03e0f3a65e4da497c3b7b213c68943cbc73a2e34.tar.xz
linux-03e0f3a65e4da497c3b7b213c68943cbc73a2e34.zip
nvme-pci: avoid dereference of symbol from unloaded module
The 'remove_work' may be scheduled to run after nvme_remove() returns since we can't simply cancel it in nvme_remove() for avoiding deadlock. Once nvme_remove() returns, this module(nvme) can be unloaded. On the other hand, nvme_put_ctrl() calls ctr->ops->free_ctrl which may point to nvme_pci_free_ctrl() in unloaded module. This patch avoids this issue by queuing 'remove_work' via 'nvme_wq', and flush this worqueue in nvme_exit() as suggested by Sagi. Suggested-by: Sagi Grimberg <sagi@grimberg.me> Signed-off-by: Ming Lei <ming.lei@redhat.com> Reviewed-by: Keith Busch <keith.busch@intel.com> Reviewed-by: Sagi Grimberg <sagi@grimberg.me> Signed-off-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'drivers/nvme/target/discovery.c')
0 files changed, 0 insertions, 0 deletions