linux-kernel - [crash] Re: [PATCH 0/4] x86_64: Optimize percpu accesses

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]

Message-ID: <20080728155248.GA7123@elte.hu>
Date:	Mon, 28 Jul 2008 17:52:48 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Mike Travis <travis@....com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Hugh Dickins <hugh@...itas.com>,
	Jack Steiner <steiner@....com>,
	Jeremy Fitzhardinge <jeremy@...p.org>,
	"H. Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org,
	Thomas Gleixner <tglx@...utronix.de>
Subject: [crash] Re: [PATCH 0/4] x86_64: Optimize percpu accesses


ok, i have integrated tip/x86/percpu-zerobased into tip/master briefly, 
but it blew up almost immediately in testing, on two boxes.

one bad config is:

  http://redhat.com/~mingo/misc/config-Mon_Jul_28_17_35_00_CEST_2008.bad

failure pattern: it booted up fine to userspace and seemed function, but 
then produced a spontaneous reboot while building a kernel, without any 
log entries.

other bad config is:

  http://redhat.com/~mingo/misc/config-Mon_Jul_28_17_30_39_CEST_2008.bad

failure pattern: early crash at:

  PANIC: early exception 0e rip 10:fffffff817dfc1a error 0 cr2 28

which corresponds to:

ffffffff817dfc0f <machine_specific_memory_setup>:
ffffffff817dfc0f:       48 8b 05 aa cf 04 00    mov    315306(%rip),%rax
# ffffffff8182cbc0 <x86_quirks>
ffffffff817dfc16:       55                      push   %rbp
ffffffff817dfc17:       48 89 e5                mov    %rsp,%rbp
ffffffff817dfc1a:       48 8b 40 28             mov    0x28(%rax),%rax  [*]
ffffffff817dfc1e:       48 85 c0                test   %rax,%rax

i.e. RAX was zero.

i've pushed out the tip/tmp.x86/percpu-zerobased.bad branch which shows 
the exact kernel that failed. It was generated by:

 git-checkout tip/master
 git-merge tip/x86/percpu-zerobased

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/