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

Groups > linux.kernel > #1272342 > unrolled thread

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

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: [lkp] [x86/entry/vsyscall] 3dc33bd30f: Kernel panic - not  syncing: Attempted to kill init! exitcode=0x0000000b Andy Lutomirski <luto@amacapital.net> - 2015-11-18 17:20 +0100

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

On Tue, Nov 17, 2015 at 10:34 PM, kernel test robot
<ying.huang@linux.intel.com> wrote:
> FYI, we noticed the below changes on
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 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?

--Andy
--
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] | [standalone]

Back to top | Article view | linux.kernel

csiph-web