nvme: queue ns scanning and async request from nvme_wq (c669ccdc) · Commits · 戴 / test

To suppress the warning triggered by nvme_uninit_ctrl: kernel: [ 50.350439] nvme nvme0: rescanning kernel: [ 50.363351] ------------[ cut here]------------ kernel: [ 50.363396] WARNING: CPU: 1 PID: 37 at kernel/workqueue.c:2423 check_flush_dependency+0x11f/0x130 kernel: [ 50.363409] workqueue: WQ_MEM_RECLAIM nvme-wq:nvme_del_ctrl_work [nvme_core] is flushing !WQ_MEM_RECLAIM events:nvme_scan_work [nvme_core] This was triggered with nvme-loop, but can happen with rdma/pci as well afaict. Signed-off-by:

Sagi Grimberg <sagi@grimberg.me> Signed-off-by:

Christoph Hellwig <hch@lst.de>

drivers/nvme/host/core.c

+3 −3

Original line number	Diff line number	Diff line
		@@ -2228,7 +2228,7 @@ void nvme_queue_scan(struct nvme_ctrl *ctrl)
		* removal.
		*/
		if (ctrl->state == NVME_CTRL_LIVE)
		schedule_work(&ctrl->scan_work);
		queue_work(nvme_wq, &ctrl->scan_work);
		}
		EXPORT_SYMBOL_GPL(nvme_queue_scan);

		@@ -2283,7 +2283,7 @@ void nvme_complete_async_event(struct nvme_ctrl *ctrl, __le16 status,
		/FALLTHRU/
		case NVME_SC_ABORT_REQ:
		++ctrl->event_limit;
		schedule_work(&ctrl->async_event_work);
		queue_work(nvme_wq, &ctrl->async_event_work);
		break;
		default:
		break;
		@@ -2306,7 +2306,7 @@ EXPORT_SYMBOL_GPL(nvme_complete_async_event);
		void nvme_queue_async_events(struct nvme_ctrl *ctrl)
		{
		ctrl->event_limit = NVME_NR_AERS;
		schedule_work(&ctrl->async_event_work);
		queue_work(nvme_wq, &ctrl->async_event_work);
		}
		EXPORT_SYMBOL_GPL(nvme_queue_async_events);

Admin message