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
| ||
|
Date: Wed, 23 Oct 2013 00:01:24 +0900 From: HATAYAMA Daisuke <d.hatayama@...fujitsu.com> To: hpa@...ux.intel.com, ebiederm@...ssion.com, vgoyal@...hat.com Cc: kexec@...ts.infradead.org, linux-kernel@...r.kernel.org, bp@...en8.de, akpm@...ux-foundation.org, fengguang.wu@...el.com, jingbai.ma@...com Subject: [PATCH v4 1/3] x86, apic: Don't count the CPU with BP flag from MP table as booting-up CPU If crash occurs on some AP, then kdump 2nd kernel is booted up on the AP. Therefore, it is not always correct that the CPU that is currently booting up the kernel is BSP. It's wrong to reflect BSP information in MP table as for the current booting up CPU. Also, boot_cpu_physical_apicid has already been initialized before reaching here, for example, in register_lapic_address(). This is a preparation for next patch that will introduce a new kernel parameter to disabls specified CPU where boot_cpu_physical_apicid needs to have apicid for the currently booting up CPU to identify it to avoid falsely disabling it. Signed-off-by: HATAYAMA Daisuke <d.hatayama@...fujitsu.com> --- arch/x86/kernel/mpparse.c | 1 - 1 file changed, 1 deletion(-) diff --git a/arch/x86/kernel/mpparse.c b/arch/x86/kernel/mpparse.c index d2b5648..969bb9f 100644 --- a/arch/x86/kernel/mpparse.c +++ b/arch/x86/kernel/mpparse.c @@ -64,7 +64,6 @@ static void __init MP_processor_info(struct mpc_cpu *m) if (m->cpuflag & CPU_BOOTPROCESSOR) { bootup_cpu = " (Bootup-CPU)"; - boot_cpu_physical_apicid = m->apicid; } printk(KERN_INFO "Processor #%d%s\n", m->apicid, bootup_cpu); -- 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/
Powered by blists - more mailing lists