From: Yang Yang <yang.yang@vivo.com>
To: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Yang Yang <yang.yang@vivo.com>
Subject: [RFC PATCH] blk-mq: fix potential I/O hang caused by batch wakeup
Date: Mon, 20 May 2024 11:38:46 +0800 [thread overview]
Message-ID: <20240520033847.13533-1-yang.yang@vivo.com> (raw)
The depth is 62, and the wake_batch is 8. In the following situation,
the task would hang forever.
t1: t2: t3:
blk_mq_get_tag . .
io_schedule . .
elevator_switch .
blk_mq_freeze_queue .
blk_freeze_queue_start .
blk_mq_freeze_queue_wait .
blk_mq_submit_bio
__bio_queue_enter
Fix this issue by waking up all the waiters sleeping on tags after
freezing the queue.
Signed-off-by: Yang Yang <yang.yang@vivo.com>
---
block/blk-core.c | 2 --
block/blk-mq.c | 4 +++-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/block/blk-core.c b/block/blk-core.c
index a16b5abdbbf5..e1eacfad6e5b 100644
--- a/block/blk-core.c
+++ b/block/blk-core.c
@@ -298,8 +298,6 @@ void blk_queue_start_drain(struct request_queue *q)
* prevent I/O from crossing blk_queue_enter().
*/
blk_freeze_queue_start(q);
- if (queue_is_mq(q))
- blk_mq_wake_waiters(q);
/* Make blk_queue_enter() reexamine the DYING flag. */
wake_up_all(&q->mq_freeze_wq);
}
diff --git a/block/blk-mq.c b/block/blk-mq.c
index 4ecb9db62337..9eb3139e713a 100644
--- a/block/blk-mq.c
+++ b/block/blk-mq.c
@@ -125,8 +125,10 @@ void blk_freeze_queue_start(struct request_queue *q)
if (++q->mq_freeze_depth == 1) {
percpu_ref_kill(&q->q_usage_counter);
mutex_unlock(&q->mq_freeze_lock);
- if (queue_is_mq(q))
+ if (queue_is_mq(q)) {
+ blk_mq_wake_waiters(q);
blk_mq_run_hw_queues(q, false);
+ }
} else {
mutex_unlock(&q->mq_freeze_lock);
}
--
2.34.1
next reply other threads:[~2024-05-20 3:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-20 3:38 Yang Yang [this message]
2024-05-20 18:11 ` [RFC PATCH] blk-mq: fix potential I/O hang caused by batch wakeup Bart Van Assche
2024-05-21 11:25 ` YangYang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240520033847.13533-1-yang.yang@vivo.com \
--to=yang.yang@vivo.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox