Hannes Reinecke 8730c1ddb6 nvme-fc: use separate work queue to avoid warning
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>
2019-05-13 16:00:03 +02:00
..
2019-04-15 16:48:51 -07:00
2019-03-06 09:41:12 -08:00
2019-03-16 13:05:32 -07:00
2019-03-29 03:04:47 +01:00
2019-03-06 14:18:59 -08:00
2019-03-15 14:37:46 -07:00
2019-03-10 11:54:48 -07:00
2019-04-22 09:47:36 -06:00
2019-03-10 10:17:23 -07:00
2019-03-14 09:00:06 -07:00
2019-04-22 09:47:36 -06:00
2019-03-09 14:57:08 -08:00
2019-03-16 12:51:50 -07:00
2019-03-06 09:41:12 -08:00
2019-03-29 15:31:16 +01:00
2019-04-10 22:45:38 -07:00
2019-03-15 14:22:59 -07:00
2019-03-11 11:22:15 -07:00
2019-04-22 09:47:36 -06:00
2019-03-10 12:29:52 -07:00