From: Ming Lei <ming.lei@redhat.com>
To: Mauricio Faria de Oliveira <mauricfo@linux.vnet.ibm.com>
Cc: Bart Van Assche <Bart.VanAssche@wdc.com>,
"chenxiang66@hisilicon.com" <chenxiang66@hisilicon.com>,
"hch@infradead.org" <hch@infradead.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"axboe@fb.com" <axboe@fb.com>, "osandov@fb.com" <osandov@fb.com>,
"hare@suse.com" <hare@suse.com>,
"wenxiong@us.ibm.com" <wenxiong@us.ibm.com>,
"linuxarm@huawei.com" <linuxarm@huawei.com>
Subject: Re: [PATCH V2 0/2] block: fix queue freeze and cleanup
Date: Sat, 2 Dec 2017 08:49:54 +0800 [thread overview]
Message-ID: <20171202004953.GB24521@ming.t460p> (raw)
In-Reply-To: <ea717cce-a083-1fef-362f-6c302b4434fa@linux.vnet.ibm.com>
On Fri, Dec 01, 2017 at 04:49:31PM -0200, Mauricio Faria de Oliveira wrote:
> Hi Bart,
>
> On 12/01/2017 02:08 PM, Bart Van Assche wrote:
> > The test chenxiang ran does not prove that there is anything wrong with v2.
> > Maybe chenxiang hit the issue described inhttps://lkml.org/lkml/2017/9/5/381?
>
> Unfortunately v2 has been found to exhibit another problem, an Oops in
> the systemd shutdown path for device-mapper LVM volumes at least, when
> calling 'q->request_fn(q)' if 'q->request_fn' is NULL.
That issue can be fixed easily in V2 and we understand DM's case clearly.
But the most important thing is that V2 can't fix Chenxiang's issue, but
V3/V1 can.
--
Ming
next prev parent reply other threads:[~2017-12-02 0:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-23 4:47 [PATCH V2 0/2] block: fix queue freeze and cleanup Ming Lei
2017-11-23 4:47 ` [PATCH V2 1/2] block: run queue before waiting for q_usage_counter becoming zero Ming Lei
2017-11-27 12:15 ` Mauricio Faria de Oliveira
2017-11-23 4:48 ` [PATCH V2 2/2] block: drain blkcg part of request_queue in blk_cleanup_queue() Ming Lei
2017-11-27 12:15 ` Mauricio Faria de Oliveira
2017-11-27 12:41 ` [PATCH V2 0/2] block: fix queue freeze and cleanup Ming Lei
2017-11-29 2:57 ` chenxiang (M)
2017-11-29 4:54 ` Ming Lei
2017-11-29 5:40 ` chenxiang (M)
2017-12-01 15:36 ` Mauricio Faria de Oliveira
2017-12-01 15:42 ` Ming Lei
2017-12-01 16:08 ` Bart Van Assche
2017-12-01 17:35 ` Ming Lei
2017-12-01 18:49 ` Mauricio Faria de Oliveira
2017-12-02 0:49 ` Ming Lei [this message]
2017-12-04 12:31 ` Mauricio Faria de Oliveira
2017-12-13 21:49 ` Bart Van Assche
2017-12-20 14:34 ` Mauricio Faria de Oliveira
2017-12-13 21:53 ` Bart Van Assche
2017-12-15 7:58 ` chenxiang (M)
2017-12-15 17:44 ` Bart Van Assche
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=20171202004953.GB24521@ming.t460p \
--to=ming.lei@redhat.com \
--cc=Bart.VanAssche@wdc.com \
--cc=axboe@fb.com \
--cc=chenxiang66@hisilicon.com \
--cc=hare@suse.com \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linuxarm@huawei.com \
--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 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.