summaryrefslogtreecommitdiff
path: root/drivers/clk/clk-s2mps11.c
diff options
context:
space:
mode:
authorHannes Reinecke <hare@suse.de>2019-05-03 12:43:52 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2019-09-16 09:21:44 +0300
commit480101a4aea26d908c920acb8c50656cbada5fec (patch)
tree15a009a651b3d6aa4da7eb670b127c49d218ad4f /drivers/clk/clk-s2mps11.c
parent5f147150b75307c8c0220ec4a4bd4f9a82018a54 (diff)
downloadlinux-480101a4aea26d908c920acb8c50656cbada5fec.tar.xz
nvme-fc: use separate work queue to avoid warning
[ Upstream commit 8730c1ddb69bdeeb10c1f613a4e15e95862b1981 ] When tearing down a controller the following warning is issued: WARNING: CPU: 0 PID: 30681 at ../kernel/workqueue.c:2418 check_flush_dependency This happens as the err_work workqueue item is scheduled on the system workqueue (which has WQ_MEM_RECLAIM not set), but is flushed from a workqueue which has WQ_MEM_RECLAIM set. Fix this by providing an FC-NVMe specific workqueue. Fixes: 4cff280a5fcc ("nvme-fc: resolve io failures during connect") Signed-off-by: Hannes Reinecke <hare@suse.com> Reviewed-by: James Smart <james.smart@broadcom.com> Signed-off-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'drivers/clk/clk-s2mps11.c')
0 files changed, 0 insertions, 0 deletions