Re: [lkp] [x86/entry/vsyscall] 3dc33bd30f: Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b

From: Andy Lutomirski
Date: Wed Nov 18 2015 - 11:17:52 EST

On Tue, Nov 17, 2015 at 10:34 PM, kernel test robot
<ying.huang@xxxxxxxxxxxxxxx> wrote:
> FYI, we noticed the below changes on
> master
> commit 3dc33bd30f3e1c1bcaaafa3482737694debf0f0b ("x86/entry/vsyscall: Add CONFIG to control default")

This is intentional. if you flip the default to disable vsyscalls,
then you need newer userspace code.

Can you either teach kbuild not to do that or rebuild your userspace
using an updated libc?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at