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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
