linux-kernel - Re: [PATCH v3 6/6] x86/cpufeature: Blacklist SPEC

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1516816701.13558.168.camel@infradead.org>
Date:   Wed, 24 Jan 2018 17:58:21 +0000
From:   David Woodhouse <dwmw2@...radead.org>
To:     Greg KH <gregkh@...ux-foundation.org>
Cc:     arjan@...ux.intel.com, tglx@...utronix.de, karahmed@...zon.de,
        x86@...nel.org, linux-kernel@...r.kernel.org,
        tim.c.chen@...ux.intel.com, bp@...en8.de, peterz@...radead.org,
        pbonzini@...hat.com, ak@...ux.intel.com,
        torvalds@...ux-foundation.org, dave.hansen@...el.com,
        gnomes@...rguk.ukuu.org.uk
Subject: Re: [PATCH v3 6/6] x86/cpufeature: Blacklist SPEC_CTRL on early
 Spectre v2 microcodes

On Wed, 2018-01-24 at 18:29 +0100, Greg KH wrote:
> 
> > +     /* Dropped repeat of SKX 50654, 0x200003c */
> 
> Nit, but why comment that you dropped a repeat?  No one cares, do they?
> You already said above where this info came from.

I started off by pedantically noted everywhere I'd had to proof-read
Intel's doc for them, so that people could map my table back to the
original and check my working. Eventually I got bored of that, but
these ones are left over. I'll kill them.

Download attachment "smime.p7s" of type "application/x-pkcs7-signature" (5213 bytes)