From: Mike Snitzer <snitzer@redhat.com>
To: Joel Stanley <joel@jms.id.au>
Cc: dm-devel@redhat.com, linuxppc-dev@lists.ozlabs.org
Subject: Re: ppc64le crash in dm on 4.1+
Date: Thu, 30 Apr 2015 11:18:18 -0400 [thread overview]
Message-ID: <20150430151818.GA30542@redhat.com> (raw)
In-Reply-To: <CACPK8XeQjdmwFScvEDMo4ie7=-e6WfW0cvW=NMLqC+zpOOJeTg@mail.gmail.com>
On Wed, Apr 29 2015 at 11:29pm -0400,
Joel Stanley <joel@jms.id.au> wrote:
> Hello,
>
> I just booted 3d99e3fe13d473ac4578c37f477a59b829530764 (linus' tree as
> of this morning) on a Tuletta and got the following:
This is fixed with the following commit (which I just sent to Linus for
4.1-rc2 inclusion):
https://git.kernel.org/cgit/linux/kernel/git/device-mapper/linux-dm.git/commit/?h=for-next&id=aa6df8dd28c01d9a3d2cfcfe9dd0a4a334d1cd81
next prev parent reply other threads:[~2015-04-30 15:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 3:29 ppc64le crash in dm on 4.1+ Joel Stanley
2015-04-30 15:18 ` Mike Snitzer [this message]
2015-04-30 15:24 ` Joel Stanley
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=20150430151818.GA30542@redhat.com \
--to=snitzer@redhat.com \
--cc=dm-devel@redhat.com \
--cc=joel@jms.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
/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).