Sagi Grimberg ddd2b8de9f nvmet: fix workqueue MEM_RECLAIM flushing dependency ... The keep alive timer needs to stay on nvmet_wq, and not modified to reschedule on the system_wq. This fixes a warning: ------------[ cut here ]------------ workqueue: WQ_MEM_RECLAIM nvmet-wq:nvmet_rdma_release_queue_work [nvmet_rdma] is flushing !WQ_MEM_RECLAIM events:nvmet_keep_alive_timer [nvmet] WARNING: CPU: 3 PID: 1086 at kernel/workqueue.c:2628 check_flush_dependency+0x16c/0x1e0 Reported-by: Yi Zhang <yi.zhang@redhat.com> Fixes: 8832cf9221 ("nvmet: use a private workqueue instead of the system workqueue") Signed-off-by: Sagi Grimberg <sagi@grimberg.me> Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com> Signed-off-by: Christoph Hellwig <hch@lst.de>		2022-10-19 12:43:13 +02:00
..
common	nvmet-auth: fix a couple of spelling mistakes	2022-08-02 17:22:51 -06:00
host	nvme-hwmon: kmalloc the NVME SMART log buffer	2022-10-19 12:43:13 +02:00
target	nvmet: fix workqueue MEM_RECLAIM flushing dependency	2022-10-19 12:43:13 +02:00
Kconfig	nvme: implement In-Band authentication	2022-08-02 17:14:49 -06:00
Makefile	nvme: implement In-Band authentication	2022-08-02 17:14:49 -06:00