linux-kernel - Re: BAD APICID ?

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]

Date:	Mon, 7 Nov 2011 18:54:02 +0100
From:	Borislav Petkov <bp@...64.org>
To:	Dave Jones <davej@...hat.com>
Cc:	x86@...nel.org, Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: BAD APICID ?

On Mon, Nov 07, 2011 at 12:39:48PM -0500, Dave Jones wrote:
> We got a report from a Fedora user hitting a WARN_ON in the apic setup code.
> 
> Here..
> 
> 1230 #ifdef CONFIG_X86_32
> 1231         /*
> 1232          * APIC LDR is initialized.  If logical_apicid mapping was
> 1233          * initialized during get_smp_config(), make sure it matches the
> 1234          * actual value.
> 1235          */
> 1236         i = early_per_cpu(x86_cpu_to_logical_apicid, cpu);
> 1237         WARN_ON(i != BAD_APICID && i != logical_smp_processor_id());
> 1238         /* always use the value from LDR */
> 1239         early_per_cpu(x86_cpu_to_logical_apicid, cpu) =
> 1240                 logical_smp_processor_id();
> 
> The full report is at https://bugzilla.redhat.com/show_bug.cgi?id=743930
> 
> Report is against our 3.0 builds, but that code look unchanged in 3.1 too,
> and even in current Linus head.
> 
> Any thoughts on what could cause this ?

Already fixed upstream: 838312be46f3abfbdc175f81c3e54a857994476d

Here's the whole thread: http://lkml.org/lkml/2011/10/14/231

HTH.

-- 
Regards/Gruss,
Boris.

Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
GM: Alberto Bozzo
Reg: Dornach, Landkreis Muenchen
HRB Nr. 43632 WEEE Registernr: 129 19551
--
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/