Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Yocto Project, Spectre and Meltdown
Date: Tue, 16 Jan 2018 11:38:06 +0000	[thread overview]
Message-ID: <1516102686.29722.267.camel@linuxfoundation.org> (raw)

I just wanted to give people an update on where the project stands
with these issues.

We currently have three stable branches we're maintaining, rocko, pyro
and morty.

GCC:
====

Patches to support fixes have now made it into the upstream gcc master
branch. We'll be looking to port these patches to the default gcc
version in the stable releases and master. Version wise, the releases
contain:

master: 7.2
rocko: 7.2 6.3
pyro: 6.3 5.4
morty: 6.2 and 5.4

so we'll likely port to 7.2, 6.3 and 6.2.

If you need something to experiment with in the meantime, Juro did put
together:

http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=jurob/gcc-patch_1

which is one of the older versions of the patchset. We have decided to
wait until something landed upstream due to the amount of discussion
around the patches before taking something to merge into master.


Kernel:
=======

There are a lot of patches around, some have made it into mainline,
some have been backported and some haven't made mainline yet. There are
reported stability issues on the stable branches and therefore we've
not pulled those in yet as they don't appear ready. As and when things
do make the stable trees, we'll pull them in and update the relevant
kernel versions.

There is a meta-intel experimental patch for 4.14 available:

http://git.yoctoproject.org/cgit.cgi/meta-intel-contrib/log/?h=clsulliv/clear-test
(also shows you to append to gcc to have the relevant gcc patch above
available)

Once there is a known good patchset, we'll look at filling in any
kernel version gaps for default kernel versions if there aren't
upstream patches/plans.


IA Microcode:
=============

There is an IA microcode update available in meta-intel:

http://git.yoctoproject.org/cgit.cgi/meta-intel/commit/?id=7969d8e442bdefd8036a334ca9d9ce133272399b


Webkit:
=======

The new webkit release which includes fixes related to this has already
been updated in master and the three stable releases (thanks Alex!).



If anyone knows of any other patches merged upstream to address related
issues please do let us know, I've tried to collate together here the
pieces I'm aware of. If there are other pieces of software that need
updates as a result of this, please also let me know.

Cheers,

Richard


             reply	other threads:[~2018-01-16 11:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-16 11:38 Richard Purdie [this message]
2018-01-27 16:35 ` Yocto Project, Spectre and Meltdown 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
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=1516102686.29722.267.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.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