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: 4cff280a5f ("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
..
host	nvme-fc: use separate work queue to avoid warning	2019-05-13 16:00:03 +02:00
target	nvmet: protect discovery change log event list iteration	2019-05-01 09:18:47 -04:00
Kconfig	nvme: use menu Kconfig interface	2017-10-04 09:43:57 +02:00
Makefile	nvmet: add a generic NVMe target	2016-07-05 11:30:33 -06:00