From: Mike Snitzer <snitzer@redhat.com>
To: Valdis Kletnieks <Valdis.Kletnieks@vt.edu>
Cc: Alasdair Kergon <agk@redhat.com>,
linux-kernel@vger.kernel.org, dm-devel@redhat.com
Subject: Re: Next-20151009 - crash during boot
Date: Mon, 12 Oct 2015 18:14:35 -0400 [thread overview]
Message-ID: <20151012221435.GA9456@redhat.com> (raw)
In-Reply-To: <7951.1444686608@turing-police.cc.vt.edu>
On Mon, Oct 12 2015 at 5:50pm -0400,
Valdis Kletnieks <Valdis.Kletnieks@vt.edu> wrote:
> Next-20151009 crashes early in boot (right after I feed cryptsetup
> the passphrase for my root filesystem).
>
> (Yes, the kernel is 10 commits past linux-next - they're all cleanup patches for
> drivers/staging that shouldn't enter into it)
>
> It appears to possibly be the same one reported by the "Linux Test Robot",
> which called this out:
>
> commit e817ef9b89e5bbfdb2a67ca9896909f414b2af91 ("dm ioctl: use kvfree() in free_params()")
Yes, that commit was dropped last week. Today's linux-next won't have
this problem. Feel free to revert e817ef9b89e5bbfdb2a67ca9896909 from
your local tree to work-around this.
prev parent reply other threads:[~2015-10-12 22:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-12 21:50 Next-20151009 - crash during boot Valdis Kletnieks
2015-10-12 22:14 ` Mike Snitzer [this message]
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=20151012221435.GA9456@redhat.com \
--to=snitzer@redhat.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.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