From: Ming Lei <ming.lei@redhat.com>
To: Jens Axboe <axboe@fb.com>,
linux-block@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>
Cc: Omar Sandoval <osandov@fb.com>,
Bart Van Assche <bart.vanassche@sandisk.com>,
Hannes Reinecke <hare@suse.com>,
chenxiang <chenxiang66@hisilicon.com>,
Mauricio Faria de Oliveira <mauricfo@linux.vnet.ibm.com>,
Wen Xiong <wenxiong@us.ibm.com>
Subject: Re: [PATCH V3] block: drain queue before waiting for q_usage_counter becoming zero
Date: Thu, 21 Dec 2017 07:12:14 +0800 [thread overview]
Message-ID: <20171220231213.GA15493@ming.t460p> (raw)
In-Reply-To: <20171129235635.20292-1-ming.lei@redhat.com>
On Thu, Nov 30, 2017 at 07:56:35AM +0800, Ming Lei wrote:
> Now we track legacy requests with .q_usage_counter in commit 055f6e18e08f
> ("block: Make q_usage_counter also track legacy requests"), but that
> commit never runs and drains legacy queue before waiting for this counter
> becoming zero, then IO hang is caused in the test of pulling disk during IO.
>
> This patch fixes the issue by draining requests before waiting for
> q_usage_counter becoming zero, both Mauricio and chenxiang reported this
> issue, and observed that it can be fixed by this patch.
>
> Link: https://marc.info/?l=linux-block&m=151192424731797&w=2
> Fixes: 055f6e18e08f("block: Make q_usage_counter also track legacy requests")
> Cc: Wen Xiong <wenxiong@us.ibm.com>
> Tested-by: "chenxiang (M)" <chenxiang66@hisilicon.com>
> Tested-by: Mauricio Faria de Oliveira <mauricfo@linux.vnet.ibm.com>
> Signed-off-by: Ming Lei <ming.lei@redhat.com>
> ---
> V3:
> - V2 can't cover chenxiang's issue, so we have to drain queue via
> blk_drain_queue(), and fallback to original post(V1)
Hi Jens,
This patch fixes regression caused by 055f6e18e08f merged to v4.15-rc,
could you consider it for v4.15?
Thanks,
Ming
next prev parent reply other threads:[~2017-12-20 23:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 23:56 [PATCH V3] block: drain queue before waiting for q_usage_counter becoming zero Ming Lei
2017-12-20 23:12 ` Ming Lei [this message]
2018-01-05 16:10 ` Jens Axboe
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=20171220231213.GA15493@ming.t460p \
--to=ming.lei@redhat.com \
--cc=axboe@fb.com \
--cc=bart.vanassche@sandisk.com \
--cc=chenxiang66@hisilicon.com \
--cc=hare@suse.com \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=mauricfo@linux.vnet.ibm.com \
--cc=osandov@fb.com \
--cc=wenxiong@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox