linux-kernel - Re: [PATCH] x86/boot: Reorganize and clean up the BIOS area reservation code

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: <C93E1967-9136-495E-AF15-C8A13E0F9328@zytor.com>
Date:	Thu, 21 Jul 2016 05:32:57 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Ingo Molnar <mingo@...nel.org>
CC:	Andy Lutomirski <luto@...nel.org>, x86@...nel.org,
	Mario Limonciello <mario_limonciello@...l.com>,
	Matthew Garrett <mjg59@...f.ucam.org>,
	linux-kernel@...r.kernel.org, Kees Cook <keescook@...omium.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: [PATCH] x86/boot: Reorganize and clean up the BIOS area reservation code

On July 21, 2016 2:11:32 AM PDT, Ingo Molnar <mingo@...nel.org> wrote:
>
>* H. Peter Anvin <hpa@...or.com> wrote:
>
>> We already reserve the first megabyte by default.  There is something
>really 
>> bizarre about this; the bug report simply doesn't seem to make any
>sense.
>
>Maybe the first megabyte reservation happens after the SMP trampoline
>allocation 
>and hence the EBDA/BIOS reservation matters to our ability to allocate
>the SMP 
>trampoline specifically?
>
>Anyway, agreed that we need more information.
>
>Thanks,
>
>	Ingo

Yes, of course - it has to.  However, 0x2c000 although braindead shouldn't be a problem.
-- 
Sent from my Android device with K-9 Mail. Please excuse brevity and formatting.