[PATCH] nvmet: fix workqueue MEM_RECLAIM flushing dependency
Chaitanya Kulkarni
chaitanyak at nvidia.com
Thu Sep 29 18:31:53 PDT 2022
>
> On Sep 27, 2022, at 11:40 PM, Sagi Grimberg <sagi at grimberg.me> wrote:
>
> 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 at redhat.com>
> Fixes: 8832cf922151 ("nvmet: use a private workqueue instead of the
> system workqueue")
> Signed-off-by: Sagi Grimberg <sagi at grimberg.me>
> ---
>
Reviewed-by: Chaitanya Kulkarni <kch at nvidia.com>
-ck
More information about the Linux-nvme
mailing list