linux-kernel - Re: [PATCH] x86/boot: Fix boot failure when SMP MP-table is based at 0

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: <20171116114012.dmjncbeocsy4assk@pd.tnic>
Date:   Thu, 16 Nov 2017 12:40:12 +0100
From:   Borislav Petkov <bp@...en8.de>
To:     Tom Lendacky <thomas.lendacky@....com>,
        "H. Peter Anvin" <hpa@...or.com>
Cc:     x86@...nel.org, Peter Zijlstra <peterz@...radead.org>,
        linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...hat.com>,
        Thomas Gleixner <tglx@...utronix.de>,
        Tomeu Vizoso <tomeu@...euvizoso.net>
Subject: Re: [PATCH] x86/boot: Fix boot failure when SMP MP-table is based at
 0

On Mon, Nov 06, 2017 at 05:00:31PM -0600, Tom Lendacky wrote:
> Btw, it was working before because instead of saving off the physical
> address as 5997efb96756 now does, it saved off a virtual address that
> pointed to physical address 0 (0xffff880000000000) and used that in the
> conditional.

Dunno, should we support any braindead vm implementation which puts
stuff in the low megabyte?

I mean, the fix is simple enough and we probably don't care all that
much whatever potent sh*t people are smoking as long as it is all the
same to the kernel...

IMO.

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.