From: David Laight <David.Laight@ACULAB.COM>
To: 'Arnd Bergmann' <arnd@arndb.de>, Alan Cox <gnomes@lxorguk.ukuu.org.uk>
Cc: Ondrej Zary <linux@rainbow-software.org>,
"whiteheadm@acm.org" <whiteheadm@acm.org>,
David Woodhouse <dwmw2@infradead.org>,
Guenter Roeck <linux@roeck-us.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Hugh Dickins" <hughd@google.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
"Jiri Kosina" <jikos@kernel.org>, Borislav Petkov <bp@alien8.de>,
Kees Cook <keescook@chromium.org>,
Jamie Iles <jamie@jamieiles.com>,
Eduardo Valentin <eduval@amazon.com>,
Laura Abbott <labbott@redhat.com>,
Rik van Riel <riel@surriel.com>,
Thomas Gleixner <tglx@linutronix.de>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: RE: [BUG] x86 : i486 reporting to be vulnerable to Meltdown/Spectre_V1/Spectre_V2
Date: Thu, 8 Feb 2018 17:02:14 +0000 [thread overview]
Message-ID: <63ca28c5acb64de5ba33a81b6da5c507@AcuMS.aculab.com> (raw)
In-Reply-To: <CAK8P3a2kuHXpJOVKux2v-B_=CrpnQBTMfV24sJqY+nQaSMf+KA@mail.gmail.com>
From: Arnd Bergmann
> Sent: 08 February 2018 15:23
...
> The Winchip is what eventually turned into the VIA Nano, which does
> have speculative execution, but I don't think the earlier C3 and C7 did,
> they are much closer to the original Winchip design.
We had terrible trouble getting (IIRC) the C7 to execute functions
that were called in 16bit mode and returned in 32bit mode and v.v.
(for boot code bios calls).
The problems seemed to imply that it was caching return addresses
and the translation (to uops) of the instructions that followed.
So it would effectively decode the first few bytes in the wrong mode.
So there might be scope for one of these attacks.
OTOH these devices were so slow that I doubt any are used for anything
serious - and certainly won't get a kernel update even if they are.
Also worth nothing that the difference between the cpu and memory
speeds is much lower - so far fewer instructions could be speculatively
executed while waiting a cache miss.
Tempting to disable everything.
David
next prev parent reply other threads:[~2018-02-08 17:02 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
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 [this message]
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=63ca28c5acb64de5ba33a81b6da5c507@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=dwmw2@infradead.org \
--cc=eduval@amazon.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--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@rainbow-software.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®