From: Jens Axboe <axboe@kernel.dk>
To: ming.lei@redhat.com, Muchun Song <muchun.song@linux.dev>
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
muchun.song@linux.dev
Subject: Re: [PATCH RESEND v3 0/3] Fix some starvation problems in block layer
Date: Wed, 16 Oct 2024 10:59:50 -0600 [thread overview]
Message-ID: <172909799069.38573.9078542205672825920.b4-ty@kernel.dk> (raw)
In-Reply-To: <20241014092934.53630-1-songmuchun@bytedance.com>
On Mon, 14 Oct 2024 17:29:31 +0800, Muchun Song wrote:
> We encounter a problem on our servers where hundreds of UNINTERRUPTED
> processes are all waiting in the WBT wait queue. And the IO hung detector
> logged so many messages about "blocked for more than 122 seconds". The
> call trace is as follows:
>
> Call Trace:
> __schedule+0x959/0xee0
> schedule+0x40/0xb0
> io_schedule+0x12/0x40
> rq_qos_wait+0xaf/0x140
> wbt_wait+0x92/0xc0
> __rq_qos_throttle+0x20/0x30
> blk_mq_make_request+0x12a/0x5c0
> generic_make_request_nocheck+0x172/0x3f0
> submit_bio+0x42/0x1c0
> ...
>
> [...]
Applied, thanks!
[1/3] block: fix missing dispatching request when queue is started or unquiesced
commit: 4bddfec1a0fb837f66b403a11ee1834769df2330
[2/3] block: fix ordering between checking QUEUE_FLAG_QUIESCED and adding requests
commit: 542c1c1b4cca00051997f4e1ad330a518e727c79
[3/3] block: fix ordering between checking BLK_MQ_S_STOPPED and adding requests
commit: 1936f2e6981297621deed9afcdc9063c1964fc5b
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2024-10-16 16:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 9:29 Muchun Song
2024-10-14 9:29 ` [PATCH RESEND v3 1/3] block: fix missing dispatching request when queue is started or unquiesced Muchun Song
2024-10-14 9:29 ` [PATCH RESEND v3 2/3] block: fix ordering between checking QUEUE_FLAG_QUIESCED and adding requests Muchun Song
2024-10-14 9:29 ` [PATCH RESEND v3 3/3] block: fix ordering between checking BLK_MQ_S_STOPPED " Muchun Song
2024-10-16 16:59 ` Jens Axboe [this message]
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=172909799069.38573.9078542205672825920.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=muchun.song@linux.dev \
/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
all inboxes | Powered by JetHome®