linux-kernel - Re: [PATCH 2/2] Enter 2nd kernel with BSP

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: <20120424080420.GA27374@one.firstfloor.org>
Date:	Tue, 24 Apr 2012 10:04:20 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	HATAYAMA Daisuke <d.hatayama@...fujitsu.com>
Cc:	andi@...stfloor.org, linux-kernel@...r.kernel.org,
	fenghua.yu@...el.com, ebiederm@...ssion.com
Subject: Re: [PATCH 2/2] Enter 2nd kernel with BSP

> native_cpu_up avoids to wake up cpu with boot_cpu_physical_apicid, but

Ok so that check needs to go then. I wonder why it is there.

> the boot_cpu_physical_apicid would be just a boot cpu now, which could
> be non-BSP on the 2nd kernel; equal to crashing cpu on the 1st
> kernel. It would need to check explicitly whether a given cpu is BSP
> or not and this would be better fix here. This is suggested by Eric.

-Andi
-- 
ak@...ux.intel.com -- Speaking for myself only.
--
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/