linux-kernel - Re: [PATCH 2/4] Revert "x86/boot: Fail the boot if !M486 and CPUID is missing"

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: <CALCETrWvHga_AFBmF5zu+RbcLjqmqABCRFToN9uNezN2Tq59yQ@mail.gmail.com>
Date:   Thu, 1 Dec 2016 09:00:51 -0800
From:   Andy Lutomirski <luto@...capital.net>
To:     Peter Zijlstra <peterz@...radead.org>
Cc:     Andy Lutomirski <luto@...nel.org>, X86 ML <x86@...nel.org>,
        One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>,
        Borislav Petkov <bp@...en8.de>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Brian Gerst <brgerst@...il.com>,
        Matthew Whitehead <tedheadster@...il.com>,
        Henrique de Moraes Holschuh <hmh@....eng.br>,
        Denys Vlasenko <dvlasenk@...hat.com>,
        "H . Peter Anvin" <hpa@...or.com>,
        Josh Poimboeuf <jpoimboe@...hat.com>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH 2/4] Revert "x86/boot: Fail the boot if !M486 and CPUID is missing"

On Wed, Nov 30, 2016 at 9:53 PM, Peter Zijlstra <peterz@...radead.org> wrote:
> On Wed, Nov 30, 2016 at 12:34:53PM -0800, Andy Lutomirski wrote:
>> This reverts commit ed68d7e9b9cfb64f3045ffbcb108df03c09a0f98.
>>
>> The patch wasn't quite correct -- there are non-Intel (and hence
>> non-486) CPUs that we support that don't have CPUID.  Since we no
>> longer require CPUID for sync_core(), just revert the patch.
>
> Might be useful to enumerate which special parts these are.

Alan thought it was Geode and Elan, right?  I can add that to the
commit message if I do a v2.

--Andy