From: "Tim Mouraveiko" <tim.ml@ipcopper.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/cpu, x86/pti: Do not enable PTI on AMD processors
Date: Wed, 03 Jan 2018 11:38:14 -0800 [thread overview]
Message-ID: <5A4D3126.11790.FCAAD77A@tim.ml.ipcopper.com> (raw)
On 12/26/2017 09:43 PM, Tom Lendacky wrote:
>AMD processors are not subject to the types of attacks that the kernel page table isolation
feature protects against.
There is no doubt this is a serious flaw. This thread reminded me - about a year ago we
discovered a software code that bricked an Intel CPU. The software code was executed and
the processor seized. The Motherboard was reset via the reset button, but the processor
never came back. It was rather dead - the CPU did not even draw any power. We contacted
Intel and one of their personnel suggested that they were aware of it. I never quite
understood if it was a processor feature or a flaw.
Tim
next reply other threads:[~2018-01-03 19:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-03 19:38 Tim Mouraveiko [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-01-03 11:07 [PATCH] x86/cpu, x86/pti: Do not enable PTI on AMD processors Ivan Ivanov
2017-12-27 5:43 Tom Lendacky
2017-12-27 8:48 ` Dave Hansen
2017-12-27 14:47 ` Tom Lendacky
2017-12-28 0:20 ` Borislav Petkov
2018-02-12 15:26 ` Pavel Machek
2018-02-12 15:37 ` Brian Gerst
2018-02-13 13:21 ` Thomas Gleixner
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=5A4D3126.11790.FCAAD77A@tim.ml.ipcopper.com \
--to=tim.ml@ipcopper.com \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).