[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1517950494.3677.30.camel@infradead.org>
Date: Tue, 06 Feb 2018 20:54:54 +0000
From: David Woodhouse <dwmw2@...radead.org>
To: whiteheadm@....org, Guenter Roeck <linux@...ck-us.net>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Hugh Dickins <hughd@...gle.com>, dave.hansen@...ux.intel.com,
jikos@...nel.org, Borislav Petkov <bp@...en8.de>,
Kees Cook <keescook@...omium.org>,
Jamie Iles <jamie@...ieiles.com>, eduval@...zon.com,
labbott@...hat.com, Rik van Riel <riel@...riel.com>,
Thomas Gleixner <tglx@...utronix.de>,
linux-kernel@...r.kernel.org
Subject: Re: [BUG] x86 : i486 reporting to be vulnerable to
Meltdown/Spectre_V1/Spectre_V2
On Tue, 2018-02-06 at 15:45 -0500, tedheadster wrote:
>
> If that is correct (and I might be wrong), then I am up to date and I
> am still getting the following in /proc/cpuinfo on my Pentium 4M i686:
>
> bugsĀ : cpu_meltdown spectre_v1 spectre_v2
That's expected for now. The CPUs we exempt are as follows:
static const __initdata struct x86_cpu_id cpu_no_speculation[] = {
{ X86_VENDOR_INTEL, 6, INTEL_FAM6_ATOM_CEDARVIEW, X86_FEATURE_ANY },
{ X86_VENDOR_INTEL, 6, INTEL_FAM6_ATOM_CLOVERVIEW, X86_FEATURE_ANY },
{ X86_VENDOR_INTEL, 6, INTEL_FAM6_ATOM_LINCROFT, X86_FEATURE_ANY },
{ X86_VENDOR_INTEL, 6, INTEL_FAM6_ATOM_PENWELL, X86_FEATURE_ANY },
{ X86_VENDOR_INTEL, 6, INTEL_FAM6_ATOM_PINEVIEW, X86_FEATURE_ANY },
{ X86_VENDOR_CENTAUR, 5 },
{ X86_VENDOR_INTEL, 5 },
{ X86_VENDOR_NSC, 5 },
{ X86_VENDOR_ANY, 4 },
{}
};
Alan is going to improve that list, but your Pentium 4 isn't on it yet.
The bugs went away on the 486 though, right?
Download attachment "smime.p7s" of type "application/x-pkcs7-signature" (5213 bytes)
Powered by blists - more mailing lists