lkml.org 
[lkml]   [2015]   [Sep]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH 1/1] blk-core: fix queue stuck on attempt to submit request from unplug
From
Date
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



\
 
 \ /
  Last update: 2015-09-28 19:41    [W:0.126 / U:0.320 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site