linux-kernel - Re: [patch] x86: 2.6.31-rc7 crash due to buggy flat_phys_pkg

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: <20090825193358.GA29968@elte.hu>
Date:	Tue, 25 Aug 2009 21:33:58 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Ravikiran G Thirumalai <kiran@...lex86.org>
Cc:	Yinghai Lu <yinghai@...nel.org>,
	Cyrill Gorcunov <gorcunov@...il.com>,
	torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org,
	shai@...lex86.org, Suresh Siddha <suresh.b.siddha@...el.com>
Subject: Re: [patch] x86: 2.6.31-rc7 crash due to buggy flat_phys_pkg_id


* Ravikiran G Thirumalai <kiran@...lex86.org> wrote:

> On Tue, Aug 25, 2009 at 11:50:56AM -0700, Yinghai Lu wrote:
> >Cyrill Gorcunov wrote:
> >
> >initial apic id and apic id could be different.
> >
> >and we should use initial apic id to get correct phys pkg id in case BIOS set crazy apic id.
> >
> 
> Is there a specific bug we are fixing here?  Again, this behavior 
> was present from atleast 2.6.15-2.6.30 on 'flat' and older 
> 'cluster' apics, and intel documentation suggests local apic be 
> used.  Is there a specific bios bug that is being fixed?
> 
> (The BIOS is not supposed to set a crazy apic ID.  The BIOS is 
> buggy in that case -- Quoting section 9.4.6 from Intel System 
> programming guide vol 3A part 1:

That means very little. If Yinghai fixed a real bug in an existing 
system we should consider it. Yinghai?

	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/