Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1241750 > unrolled thread

30c2a1faaeb3db94fc92f79553cc72634aa3b218 broke cryptsetup on my machine

Started byGiedrius Statkevičius <giedrius.statkevicius@gmail.com>
First post2015-10-07 21:30 +0200
Last post2015-10-10 15:10 +0200
Articles 4 — 3 participants

Back to article view | Back to linux.kernel


Contents

  30c2a1faaeb3db94fc92f79553cc72634aa3b218 broke cryptsetup on my  machine Giedrius Statkevičius   <giedrius.statkevicius@gmail.com> - 2015-10-07 21:30 +0200
    Re: 30c2a1faaeb3db94fc92f79553cc72634aa3b218 broke cryptsetup on my  machine Geliang Tang <geliangtang@163.com> - 2015-10-08 14:40 +0200
      Re: 30c2a1faaeb3db94fc92f79553cc72634aa3b218 broke cryptsetup on my  machine Giedrius Statkevičius   <giedrius.statkevicius@gmail.com> - 2015-10-10 14:50 +0200
        Re: 30c2a1faaeb3db94fc92f79553cc72634aa3b218 broke cryptsetup on my  machine Mike Snitzer <snitzer@redhat.com> - 2015-10-10 15:10 +0200

#1241750 — 30c2a1faaeb3db94fc92f79553cc72634aa3b218 broke cryptsetup on my machine

FromGiedrius Statkevičius <giedrius.statkevicius@gmail.com>
Date2015-10-07 21:30 +0200
Subject30c2a1faaeb3db94fc92f79553cc72634aa3b218 broke cryptsetup on my machine
Message-ID<qh2zw-5LZ-25@gated-at.bofh.it>
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [next] | [standalone]


#1242306

FromGeliang Tang <geliangtang@163.com>
Date2015-10-08 14:40 +0200
Message-ID<qhiEj-3AP-35@gated-at.bofh.it>
In reply to#1241750
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.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]


#1243885

FromGiedrius Statkevičius <giedrius.statkevicius@gmail.com>
Date2015-10-10 14:50 +0200
Message-ID<qi1L3-18e-15@gated-at.bofh.it>
In reply to#1242306

[Multipart message — attachments visible in raw view] — view raw

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>

Thanks,
Giedrius

[toc] | [prev] | [next] | [standalone]


#1243892

FromMike Snitzer <snitzer@redhat.com>
Date2015-10-10 15:10 +0200
Message-ID<qi24p-1Nd-1@gated-at.bofh.it>
In reply to#1243885
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web