From: Keith Busch <keith.busch@intel.com>
To: Mike Snitzer <snitzer@redhat.com>
Cc: Dongsu Park <dongsu.park@profitbricks.com>,
Jens Axboe <axboe@kernel.dk>, Keith Busch <keith.busch@intel.com>,
dm-devel@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: blk-mq crash with dm-multipath in for-3.20/core
Date: Mon, 9 Feb 2015 17:07:34 +0000 (UTC) [thread overview]
Message-ID: <alpine.LNX.2.00.1502091651310.15481@localhost.lm.intel.com> (raw)
In-Reply-To: <20150209164855.GB1599@redhat.com>
On Mon, 9 Feb 2015, Mike Snitzer wrote:
> On Mon, Feb 09 2015 at 11:38am -0500,
> Dongsu Park <dongsu.park@profitbricks.com> wrote:
>> So that commit 6d6285c45f5a should be either reverted, or moved to
>> linux-dm tree, doesn't it?
>>
>> Cheers,
>> Dongsu
>>
>> [1] https://www.redhat.com/archives/dm-devel/2015-January/msg00171.html
>> [2] https://git.kernel.org/cgit/linux/kernel/git/device-mapper/linux-dm.git/commit/?h=dm-for-3.20&id=102e38b1030e883efc022dfdc7b7e7a3de70d1c5
>
> Right, we're aware of this typo in 6d6285c45f5a. Sorry about that, but
> as you noted, once both the linux-block and linux-dm branches for 3.20
> are merged all is back to working.
>
> So we're planning to just leave the block commit as broken and let the
> dm commit you noted fix it up. In the end 3.20-rc1 will have a working
> dm-multipath.
Oh, we're not going rebase the series with the correction? I'm concerned
someone biscecting a completely unrelated problem might step on this
commit. Up to you guys. It's my fault, so I'll deal with the consequences.
next prev parent reply other threads:[~2015-02-09 17:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-09 16:38 Dongsu Park
2015-02-09 16:48 ` Mike Snitzer
2015-02-09 17:07 ` Keith Busch [this message]
2015-02-09 17:13 ` Mike Snitzer
2015-02-09 17:35 ` [PATCH] dm: fix multipath regression due to initializing wrong request Mike Snitzer
2015-02-09 17:47 ` Jens Axboe
2015-02-10 10:42 ` Dongsu Park
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=alpine.LNX.2.00.1502091651310.15481@localhost.lm.intel.com \
--to=keith.busch@intel.com \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=dongsu.park@profitbricks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=snitzer@redhat.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
all inboxes | Powered by JetHome®