Re: [PATCH v2 2/2] nvmet-loop: Flush nvme_delete_wq when removing the port

2019-07-05 Thread Max Gurtovoy
On 7/4/2019 2:03 AM, Logan Gunthorpe wrote: After calling nvme_loop_delete_ctrl(), the controllers will not yet be deleted because nvme_delete_ctrl() only schedules work to do the delete. This means a race can occur if a port is removed but there are still active controllers trying to access t

Re: [PATCH v2 2/2] nvmet-loop: Flush nvme_delete_wq when removing the port

2019-07-03 Thread Sagi Grimberg
Reviewed-by: Sagi Grimberg

[PATCH v2 2/2] nvmet-loop: Flush nvme_delete_wq when removing the port

2019-07-03 Thread Logan Gunthorpe
After calling nvme_loop_delete_ctrl(), the controllers will not yet be deleted because nvme_delete_ctrl() only schedules work to do the delete. This means a race can occur if a port is removed but there are still active controllers trying to access that memory. To fix this, flush the nvme_delete_