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

2017-02-23 Thread Chunyu Hu
Sorry for missing one info. Read the log and find the paniced host is running with 'fips=1', And tried without this parameter, same kernel, result are fine. so this looks like related to fips crypo or addr random. [0.00] Linux version 4.9.9-200.fc25.x86_64

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

2017-02-23 Thread Chunyu Hu
Sorry for missing one info. Read the log and find the paniced host is running with 'fips=1', And tried without this parameter, same kernel, result are fine. so this looks like related to fips crypo or addr random. [0.00] Linux version 4.9.9-200.fc25.x86_64

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

2017-02-21 Thread Kees Cook
On Tue, Feb 21, 2017 at 9:23 PM, Andy Lutomirski wrote: > On Tue, Feb 21, 2017 at 4:46 PM, Kees Cook wrote: >> On Tue, Feb 21, 2017 at 4:39 PM, Chunyu Hu wrote: >>> I hit the similar panic on Fedora 25. Is it the same issue? >>>

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

2017-02-21 Thread Kees Cook
On Tue, Feb 21, 2017 at 9:23 PM, Andy Lutomirski wrote: > On Tue, Feb 21, 2017 at 4:46 PM, Kees Cook wrote: >> On Tue, Feb 21, 2017 at 4:39 PM, Chunyu Hu wrote: >>> I hit the similar panic on Fedora 25. Is it the same issue? >>> >>> >>> [2.527391] Freeing unused kernel memory: 1688K

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

2017-02-21 Thread Andy Lutomirski
On Tue, Feb 21, 2017 at 4:46 PM, Kees Cook wrote: > On Tue, Feb 21, 2017 at 4:39 PM, Chunyu Hu wrote: >> I hit the similar panic on Fedora 25. Is it the same issue? >> >> >> [2.527391] Freeing unused kernel memory: 1688K (bdf66000 - >>

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

2017-02-21 Thread Andy Lutomirski
On Tue, Feb 21, 2017 at 4:46 PM, Kees Cook wrote: > On Tue, Feb 21, 2017 at 4:39 PM, Chunyu Hu wrote: >> I hit the similar panic on Fedora 25. Is it the same issue? >> >> >> [2.527391] Freeing unused kernel memory: 1688K (bdf66000 - >> be10c000) >> [2.535222] Write

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

2017-02-21 Thread Chunyu Hu
I have a similar call trace on Fedora25. [2.527391] Freeing unused kernel memory: 1688K (bdf66000 - be10c000) [2.535222] Write protecting the kernel read-only data: 14336k [2.542679] Freeing unused kernel memory: 1892K (94cb30827000 - 94cb30a0) [

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

2017-02-21 Thread Chunyu Hu
I have a similar call trace on Fedora25. [2.527391] Freeing unused kernel memory: 1688K (bdf66000 - be10c000) [2.535222] Write protecting the kernel read-only data: 14336k [2.542679] Freeing unused kernel memory: 1892K (94cb30827000 - 94cb30a0) [

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

2017-02-21 Thread Kees Cook
On Tue, Feb 21, 2017 at 4:39 PM, Chunyu Hu wrote: > I hit the similar panic on Fedora 25. Is it the same issue? > > > [2.527391] Freeing unused kernel memory: 1688K (bdf66000 - > be10c000) > [2.535222] Write protecting the kernel read-only data:

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

2017-02-21 Thread Kees Cook
On Tue, Feb 21, 2017 at 4:39 PM, Chunyu Hu wrote: > I hit the similar panic on Fedora 25. Is it the same issue? > > > [2.527391] Freeing unused kernel memory: 1688K (bdf66000 - > be10c000) > [2.535222] Write protecting the kernel read-only data: 14336k > [2.542679]

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

2017-02-21 Thread Kees Cook
On Fri, Feb 17, 2017 at 9:27 PM, Fengguang Wu wrote: > Hi Kees, > > It's an old patch, however the panic still happens in linux-next 20170217. What version of glibc is running in the yocto image you're booting with? For it to support CONFIG_LEGACY_VSYSCALL_NONE=y This is

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

2017-02-21 Thread Kees Cook
On Fri, Feb 17, 2017 at 9:27 PM, Fengguang Wu wrote: > Hi Kees, > > It's an old patch, however the panic still happens in linux-next 20170217. What version of glibc is running in the yocto image you're booting with? For it to support CONFIG_LEGACY_VSYSCALL_NONE=y This is reported in the second

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

2017-02-17 Thread Fengguang Wu
Hi Kees, It's an old patch, however the panic still happens in linux-next 20170217. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master commit 3dc33bd30f3e1c1bcaaafa3482737694debf0f0b Author: Kees Cook AuthorDate: Wed Aug 12 17:55:19 2015 -0700

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

2017-02-17 Thread Fengguang Wu
Hi Kees, It's an old patch, however the panic still happens in linux-next 20170217. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master commit 3dc33bd30f3e1c1bcaaafa3482737694debf0f0b Author: Kees Cook AuthorDate: Wed Aug 12 17:55:19 2015 -0700 Commit: Ingo Molnar