Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
Reply-To: whiteheadm@acm.org
In-Reply-To: <1517643438.31953.108.camel@infradead.org>
References: <CAP8WD_YnJnQW9o+t2jn6HRrY3kKQMRD44joP=thPYO5vS4ev7Q@mail.gmail.com>
 <1517643438.31953.108.camel@infradead.org>
From:   tedheadster <tedheadster@gmail.com>
Date:   Tue, 6 Feb 2018 13:33:30 -0500
Message-ID: <CAP8WD_Yrp5g6YZwV+XQTx93YpTakWEL8MD+p0bZDaPi3-r88JQ@mail.gmail.com>
Subject: Re: [BUG] x86 : i486 reporting to be vulnerable to Meltdown/Spectre_V1/Spectre_V2
To:     David Woodhouse <dwmw2@infradead.org>
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>,
        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
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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.

- Matthew