linux-kernel - 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-next>] [day] [month] [year] [list]

Message-ID: <20111107173948.GA1344@redhat.com>
Date:	Mon, 7 Nov 2011 12:39:48 -0500
From:	Dave Jones <davej@...hat.com>
To:	x86@...nel.org
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: BAD APICID ?

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 ?

	Dave

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