All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: "Giedrius Statkevičius" <giedrius.statkevicius@gmail.com>
Cc: Geliang Tang <geliangtang@163.com>,
	linux-raid <linux-raid@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 30c2a1faaeb3db94fc92f79553cc72634aa3b218 broke cryptsetup on my machine
Date: Sat, 10 Oct 2015 09:00:01 -0400	[thread overview]
Message-ID: <20151010130000.GA1079@redhat.com> (raw)
In-Reply-To: <alpine.LNX.2.20.1510101543410.1998@localhost.localdomain>

On Sat, Oct 10 2015 at  8:44P -0400,
Giedrius Statkevičius <giedrius.statkevicius@gmail.com> wrote:

> On Thu, 8 Oct 2015, Geliang Tang wrote:
> 
> > On Wed, Oct 07, 2015 at 10:27:27PM +0300, Giedrius Statkevičius wrote:
> > > Hello,
> > > I have a LUKS on LVM setup: /boot is unencrypted and everything is "hidden" in
> > > /dev/sda2. After booting on linux-next and just after entering my password
> > > cryptsetup segfaults and a stack trace is printed from the kernel. Since writing
> > > down all those numbers is hard I've made a picture where it is shown:
> > > https://i.imgur.com/6PHNUdv.jpg
> > > 
> > > I figured it had something to do with changes to memory management and thus find
> > > out that commit 30c2a1faaeb3db94fc92f79553cc72634aa3b218 broke my system.
> > > Reverting it there is no such error anymore and system boots fine past that
> > > point. 
> > > 
> > > Could someone look into this? Thanks, Giedrius
> > 
> > Bugfix for this has been sended out.
> > https://lkml.org/lkml/2015/10/8/342.
> > 
> > Thanks.
> I've tested and that fixed this issue for me. I would've replied on that thread
> but I can't find its Message-Id. Anyway, you can add:
> Tested-By: Giedrius Statkevičius <giedrius.statkevicius@gmail.com>

I dropped the original commit because I'm really not seeing the value of
using kvfree (but it was motivated by reports of crashes from ktest,
etc).  I don't have any intention of picking it back up at this point
(so Geliang's fix will go unused at this point).

Mike

      reply	other threads:[~2015-10-10 13:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-07 19:27 30c2a1faaeb3db94fc92f79553cc72634aa3b218 broke cryptsetup on my machine Giedrius Statkevičius
2015-10-08 12:38 ` Geliang Tang
2015-10-10 12:44   ` Giedrius Statkevičius
2015-10-10 13:00     ` 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=20151010130000.GA1079@redhat.com \
    --to=snitzer@redhat.com \
    --cc=geliangtang@163.com \
    --cc=giedrius.statkevicius@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.