linux-kernel - Re: [tip:x86/urgent] x86, apic: Map the local apic when parsing the MP table.

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: <4C5CB71D.1040509@kernel.org>
Date:	Fri, 06 Aug 2010 18:30:05 -0700
From:	Yinghai Lu <yinghai@...nel.org>
To:	"H. Peter Anvin" <hpa@...or.com>
CC:	"Eric W. Biederman" <ebiederm@...ssion.com>, mingo@...hat.com,
	linux-kernel@...r.kernel.org, tvrtko.ursulin@...hos.com,
	hilld@...arystorm.net, tglx@...utronix.de, hpa@...ux.intel.com,
	linux-tip-commits@...r.kernel.org
Subject: Re: [tip:x86/urgent] x86, apic: Map the local apic when parsing the
 MP table.

On 08/06/2010 06:21 PM, H. Peter Anvin wrote:
> On 08/06/2010 06:08 PM, Eric W. Biederman wrote:
>>>
>>> I'm not sure the above is decipherable.  Please provide an incremental
>>> patch with a more detailed description.
>>
>> YH was saying I overoptimized, and it looks like he is right,
>> although there are only one or two machines in existence that
>> are likely to be affected.
>>
>> Untested patch to remove the cleverness below.  It it boots all
>> is well.
>>
> 
> This makes sense to me.  Yinghai, do you have a system that is actually
> affected, and if so, could you test this patch?

no, i don't have those kind of system.

found it when i was preparing more smp_register_lapic_address patcheset.

I suggest we still keep !acpi_lapic checking, that should always right.

Yinghai


--
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/