From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
openembedded-core <openembedded-core@lists.openembedded.org>,
Paul Eggleton <paul.eggleton@linux.intel.com>
Subject: Re: Yocto Project, Spectre and Meltdown
Date: Wed, 7 Feb 2018 14:17:03 +0200 [thread overview]
Message-ID: <73704abe-4307-e1fa-bf2e-ca55617c64a7@linux.intel.com> (raw)
In-Reply-To: <1517070952.756.40.camel@linuxfoundation.org>
On 01/27/2018 06:35 PM, Richard Purdie wrote:
> On Tue, 2018-01-16 at 11:38 +0000, Richard Purdie wrote:
>> I just wanted to give people an update on where the project stands
>> with these issues.
>
> Master now contains gcc and kernel fixes (in linux-yocto). meta-yocto-
> bsp updates are still pending.
>
> rocko-next also has those fixes and is undergoing testing which if it
> passes, will get pushed to rocko.
A quick way to check what degree of protection there is on a system is
to look at what is in /sys/devices/system/cpu/vulnerabilities:
ak@linux-f9zs:/sys/devices/system/cpu/vulnerabilities> ls
meltdown spectre_v1 spectre_v2
ak@linux-f9zs:/sys/devices/system/cpu/vulnerabilities> cat spectre_v1
spectre_v2 meltdown
Vulnerable
Mitigation: Full generic retpoline
Mitigation: PTI
Of course, outdated, unprotected kernels do not have this directory at all.
Paul, perhaps this could go to release notes?
Alex
next prev parent reply other threads:[~2018-02-07 12:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 11:38 Yocto Project, Spectre and Meltdown Richard Purdie
2018-01-27 16:35 ` Richard Purdie
2018-01-27 16:59 ` Manjukumar Harthikote Matha
2018-01-27 21:34 ` Khem Raj
2018-01-27 23:06 ` Richard Purdie
2018-01-28 0:48 ` akuster808
2018-01-28 17:59 ` Manjukumar Harthikote Matha
2018-02-07 12:17 ` Alexander Kanavin [this message]
2018-02-07 18:04 ` Fathi Boudra
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=73704abe-4307-e1fa-bf2e-ca55617c64a7@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
--cc=richard.purdie@linuxfoundation.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