>From commit 20e4d813931961fe ("blk-mq: simplify queue mapping & schedule
with each possisble CPU") on, it should be easier to see unmapped hctx
in some CPU topo, such as, hctx may not be mapped to any CPU.This patch avoids the warning in __blk_mq_delay_run_hw_queue() by checking if the hctx is mapped in blk_mq_run_hw_queues(). blk_mq_run_hw_queues() is often run in SCSI or some driver's completion path, so this warning has to be addressed. Reported-by: Stefan Haberland <[email protected]> Cc: Christoph Hellwig <[email protected]> Fixes: 20e4d813931961fe ("blk-mq: simplify queue mapping & schedule with each possisble CPU") Signed-off-by: Ming Lei <[email protected]> --- block/blk-mq.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/block/blk-mq.c b/block/blk-mq.c index 16e83e6df404..48f25a63833b 100644 --- a/block/blk-mq.c +++ b/block/blk-mq.c @@ -1459,7 +1459,7 @@ void blk_mq_run_hw_queues(struct request_queue *q, bool async) int i; queue_for_each_hw_ctx(q, hctx, i) { - if (blk_mq_hctx_stopped(hctx)) + if (blk_mq_hctx_stopped(hctx) || !blk_mq_hw_queue_mapped(hctx)) continue; blk_mq_run_hw_queue(hctx, async); -- 2.9.5
