all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Meltdown / Spectre
Date: Fri, 19 Jan 2018 17:06:25 -0500	[thread overview]
Message-ID: <87bmhph5b2.fsf@netris.org> (raw)
In-Reply-To: <87po6a841k.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Tue, 16 Jan 2018 11:57:11 +0100")

ludo@gnu.org (Ludovic Courtès) writes:

> Leo Famulari <leo@famulari.name> skribis:
>
>> On Wed, Jan 10, 2018 at 05:39:59AM +0800, Alex Vong wrote:
>>> About the "Retpoline" mitigation technique[1]. Right now only GCC 7.2.0
>>> is patched, but our default gcc version is 5.4.0 in master and 5.5.0 in
>>> core-updates.  So I tried to apply the patches apply the patches to
>>> 5.5.0. There are totally 17 commits/patches. The first 3 patch can be
>>> modified to work while the 4th patch cannot be easily modified to work
>>> because the function ``ix86_nopic_noplt_attribute_p'' is not present on
>>> 5.5.0. Perhaps discarding the hunk would be fine, but we need to be
>>> careful about it (maybe running tests make sure the fix really works).
>>> 
>>> Do you think we should modify the patch to make it work on GCC 5 or
>>> update core-updates to GCC 7 instead?
>>
>> So far I haven't had time to read about Retpoline, how it works, and the
>> degree to which other mitigations work without it. So the following
>> opinion is from a place of ignorance. I'm very interested to hear what
>> everyone else thinks about your suggestion.
>>
>> Having said that, my opinion is that it's too late in this core-updates
>> cycle to change the default GCC version, especially two major versions,
>> from 5 to 7.
>
> No doubt about it.  :-)
>
>> Something we can do very easily, even on the master branch, is to build
>> specific packages with GCC 7, assuming the Retpoline technique would be
>> effective in that context.
>
> Yes, I see Alex submitted a patch already.

There's now a GCC 7.3 release candidate that apparently contains the
necessary compiler support to allow linux-libre-4.14.14 to use the
retpoline technique internally.

  https://gcc.gnu.org/ml/gcc/2018-01/msg00115.html

They hope to release GCC 7.3 on January 24th.  It would be good to
promptly add GCC 7.3 to Guix when its released, and to start using it to
build linux-libre-4.14 on selected systems: x86_64 and possibly aarch64.

I'd prefer to continue using our default compiler to build linux-libre
on systems where GCC 7.3 is not known to help with this issue.

       Mark

  reply	other threads:[~2018-01-19 22:07 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-06 13:20 What do Meltdown and Spectre mean for libreboot x200 user? Alex Vong
2018-01-06 17:23 ` Mark H Weaver
2018-01-06 17:43 ` Meltdown / Spectre Leo Famulari
2018-01-06 20:15   ` Mark H Weaver
2018-01-07  6:38     ` Mark H Weaver
2018-01-07 21:23       ` bug#30015: WebKitGTK nondeterministic build failures Mark H Weaver
2018-01-09 20:14         ` Efraim Flashner
2018-01-10  5:49         ` Leo Famulari
2020-03-22 20:40           ` Leo Famulari
2018-01-07 21:29       ` Meltdown / Spectre Mark H Weaver
2018-01-09 21:39         ` Alex Vong
2018-01-10  4:59           ` Leo Famulari
2018-01-16 10:57             ` Ludovic Courtès
2018-01-19 22:06               ` Mark H Weaver [this message]
2018-01-20  0:17                 ` Leo Famulari
2018-01-21 16:26                   ` Mark H Weaver
2018-01-24 14:23                     ` Ludovic Courtès
2018-01-24 16:19                       ` Mark H Weaver
2018-01-26 22:05                       ` Mark H Weaver
2018-01-27 16:12                         ` Ludovic Courtès
2018-01-10 15:00           ` ng0
2018-01-08 10:30       ` Ludovic Courtès
2018-01-10  5:27       ` Leo Famulari
2018-01-07  2:44   ` Chris Marusich
2018-01-08 17:22     ` Katherine Cox-Buday
2018-01-08 18:26       ` Marius Bakke
2018-01-08 21:51         ` Tobias Geerinckx-Rice
2018-01-08 22:01           ` Tobias Geerinckx-Rice
2018-01-09 20:13           ` Katherine Cox-Buday
2018-01-09 21:18             ` Tobias Geerinckx-Rice
2018-01-10  5:26               ` Leo Famulari
2018-01-11 19:45                 ` Katherine Cox-Buday
2018-01-11 21:49                   ` Adonay Felipe Nogueira
2018-01-10 10:46               ` Tobias Platen
2018-01-10 17:20                 ` Leo Famulari
2018-01-10  6:43             ` Christopher Lemmer Webber
2018-01-10 18:41               ` Kei Kebreau
2018-01-16  3:58             ` Chris Marusich
2018-01-17 19:20               ` Gábor Boskovits
2018-01-14 15:11           ` Alex Vong
2018-01-09 23:10         ` Mark H Weaver
2018-01-10  5:04           ` Leo Famulari
2018-01-16 11:10             ` Ludovic Courtès
2018-01-17  2:38               ` Mike Gerwitz
2018-01-17 14:11                 ` Ludovic Courtès
2018-01-10  9:36           ` Chris Marusich
2018-01-10 11:49             ` Adonay Felipe Nogueira
2018-01-10 12:35               ` Tobias Platen
2018-01-10 14:04                 ` Gábor Boskovits
2018-01-12  0:25                   ` Marius Bakke
2018-01-15  8:07                   ` Pjotr Prins
2018-01-16  3:08                     ` Mike Gerwitz
2018-01-16 10:04                       ` Pjotr Prins
2018-01-12  7:39                 ` Chris Marusich

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=87bmhph5b2.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.