linux

iv/linux

History

Sagi Grimberg d44ff3b100 nvmet: use a private workqueue instead of the system workqueue

[ Upstream commit 8832cf922151e9dfa2821736beb0ae2dd3968b6e ]

Any attempt to flush kernel-global WQs has possibility of deadlock
so we should simply stop using them, instead introduce nvmet_wq
which is the generic nvmet workqueue for work elements that
don't explicitly require a dedicated workqueue (by the mere fact
that they are using the system_wq).

Changes were done using the following replaces:

 - s/schedule_work(/queue_work(nvmet_wq, /g
 - s/schedule_delayed_work(/queue_delayed_work(nvmet_wq, /g
 - s/flush_scheduled_work()/flush_workqueue(nvmet_wq)/g

Reported-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Signed-off-by: Sagi Grimberg <sagi@grimberg.me>
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Sasha Levin <sashal@kernel.org>

2022-05-25 09:57:25 +02:00

admin-cmd.c

nvmet: use a private workqueue instead of the system workqueue

2022-05-25 09:57:25 +02:00

configfs.c

nvmet: use a private workqueue instead of the system workqueue

2022-05-25 09:57:25 +02:00

core.c

nvmet: use a private workqueue instead of the system workqueue

2022-05-25 09:57:25 +02:00

discovery.c

nvmet: allow mn change if subsys not discovered