From: David Woodhouse <dwmw2@infradead.org>
To: whiteheadm@acm.org, Guenter Roeck <linux@roeck-us.net>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Hugh Dickins <hughd@google.com>,
dave.hansen@linux.intel.com, jikos@kernel.org,
Borislav Petkov <bp@alien8.de>, Kees Cook <keescook@chromium.org>,
Jamie Iles <jamie@jamieiles.com>,
eduval@amazon.com, labbott@redhat.com,
Rik van Riel <riel@surriel.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: [BUG] x86 : i486 reporting to be vulnerable to Meltdown/Spectre_V1/Spectre_V2
Date: Tue, 06 Feb 2018 20:54:54 +0000 [thread overview]
Message-ID: <1517950494.3677.30.camel@infradead.org> (raw)
In-Reply-To: <CAP8WD_Ztwp3dLvv+kbQ9QizWHWCwpZnnXxQ++Z0OVnLnaj01+Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 978 bytes --]
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?
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5213 bytes --]
next prev parent reply other threads:[~2018-02-06 20:54 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-03 4:52 tedheadster
2018-02-03 7:37 ` David Woodhouse
2018-02-06 18:33 ` tedheadster
2018-02-06 19:02 ` Greg Kroah-Hartman
2018-02-06 19:10 ` David Woodhouse
2018-02-06 19:13 ` Guenter Roeck
2018-02-06 19:17 ` David Woodhouse
2018-02-06 19:24 ` tedheadster
2018-02-06 20:45 ` tedheadster
2018-02-06 20:54 ` David Woodhouse [this message]
2018-02-06 22:11 ` tedheadster
2018-02-07 8:18 ` Ondrej Zary
2018-02-08 13:49 ` Alan Cox
2018-02-08 15:22 ` Arnd Bergmann
2018-02-08 17:02 ` David Laight
2018-02-08 17:27 ` tedheadster
2018-02-08 21:50 ` Arnd Bergmann
2018-02-09 8:41 ` Ondrej Zary
2018-02-13 21:04 ` Pavel Machek
2018-02-15 9:53 ` What was last kernel that booted on hardware XY? database was Re: [BUG] x86 : i486 reporting to be vulnerable to Meltdown/Spectre_V1/Spectre_V2A Pavel Machek
2018-02-15 13:16 ` tedheadster
2018-02-17 21:16 ` Pavel Machek
2018-02-17 22:39 ` tedheadster
2018-02-23 8:07 ` Pavel Machek
2018-02-08 17:50 ` [BUG] x86 : i486 reporting to be vulnerable to Meltdown/Spectre_V1/Spectre_V2 tedheadster
2018-02-08 20:52 ` Alan Cox
2018-02-13 21:04 ` Pavel Machek
2018-02-13 23:45 ` Alan Cox
2018-02-08 21:16 ` Alan Cox
2018-02-08 21:57 ` Arnd Bergmann
2018-02-06 21:59 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1517950494.3677.30.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=eduval@amazon.com \
--cc=gregkh@linuxfoundation.org \
--cc=hughd@google.com \
--cc=jamie@jamieiles.com \
--cc=jikos@kernel.org \
--cc=keescook@chromium.org \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=riel@surriel.com \
--cc=tglx@linutronix.de \
--cc=whiteheadm@acm.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®