From: Mike Snitzer <snitzer@redhat.com>
To: axboe@kernel.dk
Cc: David Jeffery <djeffery@redhat.com>,
Ming Lei <tom.leiming@gmail.com>,
linux-block@vger.kernel.org, dm-devel@redhat.com,
Bart.VanAssche@wdc.com
Subject: Re: [for-4.16 PATCH v5 0/4] block/dm: allow DM to defer blk_register_queue() until ready
Date: Fri, 12 Jan 2018 11:13:48 -0500 [thread overview]
Message-ID: <20180112161348.GA4782@redhat.com> (raw)
In-Reply-To: <20180112150606.6037-1-snitzer@redhat.com>
On Fri, Jan 12 2018 at 10:06am -0500,
Mike Snitzer <snitzer@redhat.com> wrote:
> Hi Jens,
>
> I'm submitting this v5 with more feeling now ;)
Of course PATCH 02/04 needed a v6.
> I've distilled the changes down to be quite minimal. Hopefully this
> will help you and others review.
I could make it even simpler by dropping 02/04 entirely. But I do think
it worthwhile to try to get 02/04 in at this time too.
> I've also done a dry-run of applying 4.16 block changes and then
> merging dm-4.16; no merge conflicts:
> https://git.kernel.org/pub/scm/linux/kernel/git/snitzer/linux.git/log/?h=block-4.16
> https://git.kernel.org/pub/scm/linux/kernel/git/snitzer/linux.git/log/?h=dm-4.16
> https://git.kernel.org/pub/scm/linux/kernel/git/snitzer/linux.git/log/?h=block-4.16_dm-4.16
>
> And all tests very well for me.
>
> Please consider for 4.16, thanks!
Anyway, I've genuinely tested with blk-mq now. Sorry for all the
iterations on this patchset in such rapid succession. Obviously I know
it doesn't instill confidence...
But I really would appreciate you giving this patchset serious
consideration.
DM is long overdue for this fix.
Thanks,
Mike
next prev parent reply other threads:[~2018-01-12 16:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 15:06 [for-4.16 PATCH v5 0/4] block/dm: allow DM to defer blk_register_queue() until ready Mike Snitzer
2018-01-12 15:06 ` [for-4.16 PATCH v5 1/4] block: only bdi_unregister() in del_gendisk() if !GENHD_FL_HIDDEN Mike Snitzer
2018-01-12 15:06 ` [for-4.16 PATCH v5 2/4] block: properly protect the 'queue' kobj in blk_unregister_queue Mike Snitzer
2018-01-12 15:17 ` Ming Lei
2018-01-12 15:29 ` Mike Snitzer
2018-01-12 16:03 ` [for-4.16 PATCH v6 " Mike Snitzer
2018-01-13 12:57 ` Ming Lei
2018-01-12 15:06 ` [for-4.16 PATCH v5 3/4] block: allow gendisk's request_queue registration to be deferred Mike Snitzer
2018-01-12 15:06 ` [for-4.16 PATCH v5 4/4] dm: fix incomplete request_queue initialization Mike Snitzer
2018-01-12 16:13 ` Mike Snitzer [this message]
2018-01-15 17:16 ` [for-4.16 PATCH v5 0/4] block/dm: allow DM to defer blk_register_queue() until ready Bart Van Assche
2018-01-15 17:29 ` Mike Snitzer
2018-01-15 17:36 ` Bart Van Assche
2018-01-15 17:48 ` Mike Snitzer
2018-01-15 17:51 ` Bart Van Assche
2018-01-15 17:57 ` Mike Snitzer
2018-01-15 22:15 ` Mike Snitzer
2018-01-15 22:51 ` Bart Van Assche
2018-01-15 23:10 ` Mike Snitzer
2018-01-15 23:13 ` Mike Snitzer
2018-01-16 2:21 ` Ming Lei
2018-01-16 18:19 ` 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=20180112161348.GA4782@redhat.com \
--to=snitzer@redhat.com \
--cc=Bart.VanAssche@wdc.com \
--cc=axboe@kernel.dk \
--cc=djeffery@redhat.com \
--cc=dm-devel@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=tom.leiming@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).