From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: Re: Meltdown / Spectre Date: Fri, 19 Jan 2018 17:06:25 -0500 Message-ID: <87bmhph5b2.fsf@netris.org> References: <874lnzcedp.fsf@gmail.com> <20180106174358.GA28436@jasmine.lan> <87vageeobi.fsf@netris.org> <87incedvgv.fsf@netris.org> <87k1wtcq7m.fsf@netris.org> <87wp0qognk.fsf@gmail.com> <20180110045930.GA29390@jasmine.lan> <87po6a841k.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:35783) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eceoa-0000S9-TF for guix-devel@gnu.org; Fri, 19 Jan 2018 17:07:13 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eceoW-0000AI-V0 for guix-devel@gnu.org; Fri, 19 Jan 2018 17:07:12 -0500 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") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Ludovic =?utf-8?Q?Court=C3=A8s?= Cc: guix-devel@gnu.org ludo@gnu.org (Ludovic Court=C3=A8s) writes: > Leo Famulari 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). >>>=20 >>> 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