Skip to contentSkip to conversation

Yocto Project, Spectre and Meltdown

DISCUSSION Richard Purdie 6 participants 9 messages Jan 16, 2018 – Feb 7, 2018

lore
Share & tools
lore
#0 lore 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

#1 lore raw
Quoted 2 lines · Richard Purdie

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.

I'm not aware of gcc 6.x patches for these issues yet which will gate fixes for pyro and morty.

Cheers,

Richard

#2 lore raw

Hi RP,

Quoted 9 lines

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Richard Purdie
Sent: Saturday, January 27, 2018 8:36 AM
To: openembedded-core <[email protected]>
Subject: Re: [OE-core] Yocto Project, Spectre and Meltdown

On Tue, 2018-01-16 at 11:38 +0000, Richard Purdie wrote:

Quoted 9 lines
Quoted 2 lines

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.

I see that rocko-next branch is upgrading the GCC version to 7.3 from 7.2 , is there a reason to do so? I was under the impression that we would backport the security fixes to 7.2 version.

Thanks,
Manju

#3 lore raw
Quoted 17 lines · Manjukumar Harthikote Matha

Hi RP,

Quoted 15 lines

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Richard Purdie
Sent: Saturday, January 27, 2018 8:36 AM
To: openembedded-core <[email protected]>
Subject: Re: [OE-core] Yocto Project, Spectre and Meltdown

Quoted 2 lines · Richard Purdie

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.

Quoted 7 lines
Quoted 3 lines

rocko-next also has those fixes and is undergoing testing which if it passes, will get pushed to rocko.

I see that rocko-next branch is upgrading the GCC version to 7.3 from 7.2 , is there a reason to do so? I was under the impression that we would backport the security fixes to 7.2 version.

point releases are bugfix releases of gcc, I think you can look at it as cumulative bugfixes backport.

If you are concerned about some of the fixes in this

https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=7.3

please let us know.

-Khem

#4 lore raw
In reply to Manjukumar Harthikote Matha
Quoted 18 lines · Manjukumar Harthikote Matha

-----Original Message-----

Quoted 17 lines

From: [email protected] [mailto:[email protected]] On Behalf Of
Richard Purdie
Sent: Saturday, January 27, 2018 8:36 AM
To: openembedded-core <[email protected]>
Subject: Re: [OE-core] Yocto Project, Spectre and Meltdown

Quoted 4 lines · Richard Purdie

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.

Quoted 8 lines
Quoted 4 lines

rocko-next also has those fixes and is undergoing testing which if it passes, will get
pushed to rocko.

I see that rocko-next branch is upgrading the GCC version to 7.3 from 7.2 , is there a reason to do so?
I was under the impression that we would backport the security fixes to 7.2 version.

As Khem replied, this is the stable gcc series and gcc remapped their versioning scheme a while back to mean that 7.3 is a point release of the 7 series.

I'm of the view that the gcc team know a lot more about which patches should be backported to a stable series and have a better skillset and knowledge base to know how to apply patches onto the older versions than we do. As such I believe that 7.3 is the right approach for rocko.

Do you have a reason to believe we should do something else?

Note that for pyro and earlier we will need gcc 6 patches, we are not upgrading 6 -> 7 on pyro since that would cause a ton of breakage.

Cheers,

Richard

#5 lore raw
Quoted 26 lines · Richard Purdie
Quoted 17 lines · Manjukumar Harthikote Matha

-----Original Message-----

Quoted 16 lines

From: [email protected] [mailto:[email protected]] On Behalf Of
Richard Purdie
Sent: Saturday, January 27, 2018 8:36 AM
To: openembedded-core <[email protected]>
Subject: Re: [OE-core] Yocto Project, Spectre and Meltdown

Quoted 3 lines · Richard Purdie

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.

Quoted 8 lines
Quoted 4 lines

rocko-next also has those fixes and is undergoing testing which if it passes, will get
pushed to rocko.

I see that rocko-next branch is upgrading the GCC version to 7.3 from 7.2 , is there a reason to do so?
I was under the impression that we would backport the security fixes to 7.2 version.

Quoted 8 lines

As Khem replied, this is the stable gcc series and gcc remapped their versioning scheme a while back to mean that 7.3 is a point release of the 7 series.

I'm of the view that the gcc team know a lot more about which patches should be backported to a stable series and have a better skillset and knowledge base to know how to apply patches onto the older versions than we do. As such I believe that 7.3 is the right approach for rocko.

Agreed.

Quoted 5 lines

Do you have a reason to believe we should do something else?

Note that for pyro and earlier we will need gcc 6 patches, we are not upgrading 6 -> 7 on pyro since that would cause a ton of breakage.

Agreed. Currently  evaluating best  and safest approach.

- armin

Quoted 5 lines

Cheers,

Richard

#6 lore raw
Quoted 40 lines

-----Original Message-----
From: akuster808 [mailto:[email protected]]
Sent: Saturday, January 27, 2018 4:48 PM
To: Richard Purdie <[email protected]>; Manjukumar Harthikote Matha <[email protected]>; openembedded-core <openembedded- [email protected]>
Subject: Re: [OE-core] Yocto Project, Spectre and Meltdown

Quoted 27 lines · Richard Purdie
Quoted 15 lines · Manjukumar Harthikote Matha

-----Original Message-----

Quoted 14 lines

From: [email protected] [mailto:[email protected]] On Behalf Of Richard Purdie
Sent: Saturday, January 27, 2018 8:36 AM
To: openembedded-core <[email protected]>
Subject: Re: [OE-core] Yocto Project, Spectre and Meltdown

Quoted 2 lines · Richard Purdie

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.

Quoted 7 lines
Quoted 3 lines

rocko-next also has those fixes and is undergoing testing which if it passes, will get pushed to rocko.

I see that rocko-next branch is upgrading the GCC version to 7.3 from 7.2 , is there a reason to do so?
I was under the impression that we would backport the security fixes to 7.2 version.

As Khem replied, this is the stable gcc series and gcc remapped their versioning scheme a while back to mean that 7.3 is a point release of the 7 series.

Quoted 6 lines
Quoted 4 lines

I'm of the view that the gcc team know a lot more about which patches should be backported to a stable series and have a better skillset and knowledge base to know how to apply patches onto the older versions than we do. As such I believe that 7.3 is the right approach for rocko.

Agreed.

I thought it is a big upgrade in subsequent upgrade, hence my question.

Quoted 3 lines
Quoted 3 lines

Do you have a reason to believe we should do something else?

We have released a rocko based distribution, my fear of changing 7.2->7.3 in subsequent upgrade cycle might result in quite some extensive testing across all product ranges and application development of top. This might result in quite some churn, hence the question.

Thanks,
Manju

#7 lore raw
In reply to Richard Purdie
Quoted 9 lines · Richard Purdie
Quoted 2 lines · Richard Purdie

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

#8 lore raw
Quoted 27 lines · Alexander Kanavin
Quoted 7 lines · Richard Purdie
Quoted 3 lines · Richard Purdie

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

Quoted 5 lines

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

Quoted 4 lines

Of course, outdated, unprotected kernels do not have this directory at all.

Paul, perhaps this could go to release notes?

It might be of interest to some since it's shipped by some distro:
https://github.com/speed47/spectre-meltdown-checker

Quoted 8 lines

Alex

--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core