linux-kernel - Re: [git-pull -tip] x86: mpparse cleanup

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090318163933.GA29854@elte.hu>
Date:	Wed, 18 Mar 2009 17:39:33 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Jaswinder Singh Rajput <jaswinder@...nel.org>
Cc:	x86 maintainers <x86@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Yinghai Lu <yinghai@...nel.org>
Subject: Re: [git-pull -tip] x86: mpparse cleanup


* Ingo Molnar <mingo@...e.hu> wrote:

> >  1 files changed, 120 insertions(+), 141 deletions(-)
> 
> Looks good - pulled, thanks Jaswinder!
> 
> Would you be interested in resurrecting the more mechanic cleanups 
> you did as well, on top of this patch?
> 
> They are still valuable, we just have to keep them separate from a 
> potential breakage-causing change like the above one, so that if a 
> tester bisects to it, we have an as single-purpose and focused 
> commit to look at as possible.

So it's helpful to have a small commit when we have a regression.

Such as in this case - a -tip testbox crashed with:

weird, boot CPU (#0) not listed by the BIOS.
Kernel panic - not syncing: Boot APIC ID in local APIC unexpected (0 vs 4)
Pid: 1, comm: swapper Not tainted 
2.6.29-rc8-tip-02595-g170ae27-dirty #21111
Call Trace:
 [<c0599964>] ? printk+0x14/0x18
 [<c05998a6>] panic+0x3e/0xe8
 [<c08fc9e4>] native_smp_prepare_cpus+0x13e/0x1f8
 [<c08f335a>] kernel_init+0x47/0xd8
 [<c08f3313>] ? kernel_init+0x0/0xd8
 [<c0103ea3>] kernel_thread_helper+0x7/0x10

config and full crashlog attached.

	Ingo


View attachment "config" of type "text/plain" (62991 bytes)

View attachment "crash.log" of type "text/plain" (19492 bytes)