linux-kernel - Re: [LKP] [x86_64, vsyscall] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 15 Dec 2014 09:07:38 +0800
From:	Huang Ying <ying.huang@...ux.intel.com>
To:	Andy Lutomirski <luto@...capital.net>
Cc:	Thomas Gleixner <tglx@...utronix.de>, LKP ML <lkp@...org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [LKP] [x86_64, vsyscall] Kernel panic - not syncing: Attempted
 to kill init! exitcode=0x0000000b

On Sun, 2014-12-14 at 17:03 -0800, Andy Lutomirski wrote:
> On Sun, Dec 14, 2014 at 4:58 PM, Huang Ying <ying.huang@...ux.intel.com> wrote:
> > FYI, we noticed the below changes on
> >
> > commit 1ad83c858c7d4ea210429142c99a1548e6715a35 ("x86_64,vsyscall: Make vsyscall emulation configurable")
> >
> 
> This is expected.  You turned off an expert option, disabling
> emulation of a deprecated feature that your init needs. :)  If you
> enable that option but boot with vsyscall=none, you'll get the same
> OOPS, but you'll get a helpful error message, too.
> 
> Either force CONFIG_X86_VSYSCALL_EMULATION=y or upgrade to a modern
> gilbc and make sure you rebuild all your static binaries.

Thanks a lot for your information!  That is helpful for our testing!

Best Regards,
Huang, Ying


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