All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: whiteheadm@acm.org
Cc: David Woodhouse <dwmw2@infradead.org>,
	Hugh Dickins <hughd@google.com>,
	dave.hansen@linux.intel.com, jikos@kernel.org,
	Borislav Petkov <bp@alien8.de>,
	Guenter Roeck <linux@roeck-us.net>,
	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, 6 Feb 2018 11:02:33 -0800	[thread overview]
Message-ID: <20180206190233.GA10476@kroah.com> (raw)
In-Reply-To: <CAP8WD_Yrp5g6YZwV+XQTx93YpTakWEL8MD+p0bZDaPi3-r88JQ@mail.gmail.com>

On Tue, Feb 06, 2018 at 01:33:30PM -0500, tedheadster wrote:
> On Sat, Feb 3, 2018 at 2:37 AM, David Woodhouse <dwmw2@infradead.org> wrote:
> > On Fri, 2018-02-02 at 23:52 -0500, tedheadster wrote:
> >> I just tested the 4.15 kernel and it is reporting that my old i486
> >> (non-cpuid capable) cpu is vulnerable to all three issues: Meltdown,
> >> Spectre V1, and Spectre V2.
> >>
> >> I find this to be _unlikely_.
> >
> > This should be fixed in Linus' tree already by commit fec9434a1
> > ("x86/pti: Do not enable PTI on CPUs which are not vulnerable to
> > Meltdown").
> >
> > We'll make sure it ends up in the stable tree too, if it hasn't
> > already.
> 
> David
>   I believe I got the patch(es) you mention in in the stable 4.15.1 kernel:
> 
> Pull x86/pti updates from Thomas Gleixner: "Another set of melted
> spectrum related changes"
> (commit 6304672b7f0a5c010002e63a075160856dc4f88d).
> 
> Unfortunately, the symptoms I reported remain on at least the i486 and i686.

Can you try 4.15.2-rc1?  Or how about Linus's kernel tree now?  There
was a lot of spectrum patches merged just this week that were not in
4.15.1.

thanks,

greg k-h

  reply	other threads:[~2018-02-06 19:02 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-03  4:52 [BUG] x86 : i486 reporting to be vulnerable to Meltdown/Spectre_V1/Spectre_V2 tedheadster
2018-02-03  7:37 ` David Woodhouse
2018-02-06 18:33   ` tedheadster
2018-02-06 19:02     ` Greg Kroah-Hartman [this message]
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
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=20180206190233.GA10476@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=dwmw2@infradead.org \
    --cc=eduval@amazon.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.