From: Jens Axboe <axboe@kernel.dk>
To: Roman Pen <r.peniaev@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] blk-core: fix queue stuck on attempt to submit request from unplug
Date: Mon, 28 Sep 2015 11:27:20 -0600 [thread overview]
Message-ID: <56097878.2030000@kernel.dk> (raw)
In-Reply-To: <1443386699-5049-1-git-send-email-r.peniaev@gmail.com>
On 09/27/2015 02:44 PM, Roman Pen wrote:
> In case of several stacked block devices, which both were inited by
> blk_init_queue call, you can catch the queue stuck, if first device
> in stack makes bio submit being in a flush of a plug list.
>
> Let's consider this regular scenario taking readahead into account
> (readahead.c:read_pages):
>
> 1. Start plug
> 2. Read pages in loop
> 3. Finish plug
>
> This example generates backtrace as follows:
>
> 1. blk_start_plug
> 2. generic_make_request
> q->make_request_fn
> [blk_queue_bio]
> if (current->plug)
> list_add_tail(&req->queuelist, &plug->list);
> 3. blk_finish_plug
> blk_flush_plug_list
> queue_unplugged
> __blk_run_queue
> XXX_request_fn [some request handler of block device]
> generic_make_request
> q->make_request_fn
> [blk_queue_bio]
> if (current->plug)
> list_add_tail(&req->queuelist, &plug->list);
>
> So the problem is, that on step 3. XXX_request_fn makes
> another request, which again will be put to plug list,
> because plug is till active, thus new request will be
> stuck forever in the queue.
>
> How to fix?
> Do flush plug list till it becomes empty.
What devices submit IO from request_fn? Seems like something that would
be better handled out of a make_request_fn hook for that device, which
would also avoid this corner case.
--
Jens Axboe
next prev parent reply other threads:[~2015-09-28 17:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-27 20:44 [PATCH 1/1] blk-core: fix queue stuck on attempt to submit request from unplug Roman Pen
2015-09-28 17:27 ` Jens Axboe [this message]
2015-09-28 17:36 ` Roman Peniaev
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=56097878.2030000@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=r.peniaev@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.