f41d427cdd
When we trigger nvm target remove during device hot unplug, there is a probability to hit a general protection fault. This is caused by use of nvm_dev thay may be freed from another (hot unplug) thread (in the nvm_unregister function). Introduce lock in nvme_ioctl_dev_remove function to prevent this situation. Signed-off-by: Marcin Dziegielewski <marcin.dziegielewski@intel.com> Reviewed-by: Javier González <javier@javigon.com> Signed-off-by: Matias Bjørling <mb@lightnvm.io> Signed-off-by: Jens Axboe <axboe@kernel.dk> |
||
---|---|---|
.. | ||
core.c | ||
Kconfig | ||
Makefile | ||
pblk-cache.c | ||
pblk-core.c | ||
pblk-gc.c | ||
pblk-init.c | ||
pblk-map.c | ||
pblk-rb.c | ||
pblk-read.c | ||
pblk-recovery.c | ||
pblk-rl.c | ||
pblk-sysfs.c | ||
pblk-trace.h | ||
pblk-write.c | ||
pblk.h |