On 02/09/2015 10:35 AM, Mike Snitzer wrote:
On Mon, Feb 09 2015 at 12:13P -0500,
Mike Snitzer <snitzer@xxxxxxxxxx> wrote:
On Mon, Feb 09 2015 at 12:07pm -0500,
Keith Busch <keith.busch@xxxxxxxxx> wrote:
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.
Rebasing this late (3.20 merge already opened) is generally not done.
Unfortunately we'll just have to suck it up and deal with the fallout
during bisect -- would wager very few are bisecting with multipath as
the focus of their test.
Jens and I discussed this further and given that linux-block breaks
dm-multipath it is best to fix linux-block and let Linus resolve the
merge when I send him the linux-dm pull.
Here is the patch to fix the regression:
Added, thanks. I don't think this is worth rebasing for, so just added
to the top of for-3.20/core (since that's where the buggy commit was added).
--
Jens Axboe
--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel
