[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20140116015120.GA15735@localhost>
Date: Thu, 16 Jan 2014 09:51:20 +0800
From: Fengguang Wu <fengguang.wu@...el.com>
To: Kees Cook <keescook@...omium.org>
Cc: "H. Peter Anvin" <hpa@...ux.intel.com>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [x86, kaslr] PANIC: early exception 0e rip 10:ffffffff8ae04c6e
error 0 cr2 ffffffff81972b28
Kees,
On Wed, Jan 15, 2014 at 04:19:34PM -0800, Kees Cook wrote:
> Is it possible this is the bug that was fixed with "x86, relocs: add
> percpu fixup for GNU ld 2.23"?
>
> 82fa9637a2ba285bcc7c5050c73010b2c1b3d803 doesn't include the full
> x86,kalsr (and x86,relocs) series, so I'm not sure it's a good place
> to test.
I just tested the new tip/x86/kaslr head da2b6fb99 ("x86, kaslr:
Clarify RANDOMIZE_BASE_MAX_OFFSET") and find 4 boot failures out of
100 total boots for kconfig x86_64-randconfig-s1-01101738.
boot_successes: 96
boot_failures: 4
general_protection_fault:SMP_SMP: 2
RIP:get_pageblock_flags_group: 1
RIP:memcpy: 1
Kernel_panic-not_syncing:Fatal_exception: 2
page_allocation_failure:order:,mode: 1
BUG:kernel_boot_hang: 1
RIP:__lock_acquire: 1
RIP:free_object: 1
Attached are the dmesg files. One of them is OOM triggered by trinity,
which is not a problem.
Thanks,
Fengguang
View attachment "dmesg-yocto-nhm4-4:20140116091528:x86_64-randconfig-s1-01101738:3.12.0-rc4-00014-gda2b6fb:1" of type "text/plain" (2160 bytes)
View attachment "dmesg-quantal-roam-24:20140116090953:x86_64-randconfig-s1-01101738:3.12.0-rc4-00014-gda2b6fb:1" of type "text/plain" (86208 bytes)
View attachment "dmesg-yocto-snb-26:20140116085613:x86_64-randconfig-s1-01101738:3.12.0-rc4-00014-gda2b6fb:1" of type "text/plain" (72682 bytes)
View attachment "dmesg-quantal-cairo-16:20140116085449:x86_64-randconfig-s1-01101738:3.12.0-rc4-00014-gda2b6fb:1" of type "text/plain" (73281 bytes)
Powered by blists - more mailing lists