linux-kernel - Re: [x86] a75a3f6fc9 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: Windows password security audit tool. GUI, reports in PDF.

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

Date:   Fri, 17 Feb 2017 22:12:36 -0800
From:   Andy Lutomirski <luto@...capital.net>
To:     Fengguang Wu <fengguang.wu@...el.com>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        Andy Lutomirski <luto@...nel.org>,
        Ingo Molnar <mingo@...nel.org>, LKP <lkp@...org>
Subject: Re: [x86] a75a3f6fc9 Kernel panic - not syncing: Attempted to kill
 init! exitcode=0x0000000b

On Fri, Feb 17, 2017 at 9:42 PM, Fengguang Wu <fengguang.wu@...el.com> wrote:
> Greetings,
>
> FYI here is an old bug, however is still active in mainline kernel.
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>

> [    3.185986] init[1] vsyscall attempted with vsyscall=none ip:ffffffffff600400 cs:33 sp:7ffe878ff8b8 ax:ffffffffff600400 si:7f2c3de62a4c di:7ffe878ff978

I don't know what's up with the bisection, but I think this is a
configuration problem in your test setup.  You've configured with:

CONFIG_LEGACY_VSYSCALL_NONE=y

which is not valid when you're running binaries that are compiled with
as old a glibc as you're using.  *Dynamic* glibc binaries have been
fine for a long time, but static glibc binaried (e.g. your init, I
presume) need a glibc that's only a couple years old.

You could fix it by either disallowing that particular configuration
or by updating your distro.

--Andy