[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200115122458.GB20975@zn.tnic>
Date: Wed, 15 Jan 2020 13:24:58 +0100
From: Borislav Petkov <bp@...en8.de>
To: Arvind Sankar <nivedita@...m.mit.edu>,
"H. Peter Anvin" <hpa@...or.com>
Cc: Kees Cook <keescook@...omium.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, x86@...nel.org,
linux-kernel@...r.kernel.org,
Thomas Lendacky <Thomas.Lendacky@....com>,
Mauro Rossi <issor.oruam@...il.com>,
Michael Matz <matz@...e.de>
Subject: Re: [PATCH v3] x86/vmlinux: Fix vmlinux.lds.S with pre-2.23 binutils
On Tue, Jan 14, 2020 at 07:21:32PM -0500, Arvind Sankar wrote:
> RHEL7 looks to have been released with 2.23 and we already don't
> support the version in RHEL6, so that should be good too.
Good.
> Thumbs up from me -- I had thought there were a few other reports
> earlier about these,
Lemme clarify what I meant: I'm not aware of any other reports wrt
current kernel and ancient binutils build issues.
> but looking at those threads, it seems like they're
> all actually with ld.gold, which we already decided to drop support for
> in commit 75959d44f9dc ("kbuild: Fail if gold linker is detected").
Ok, then. So I'd say, we should do a trivial patch upping the binutils
version in Documentation/process/changes.rst with an explanation why
we're doing it. I'll queue it after 5.6-rc1 into tip and then it would
spend the maximal amount of exposure time in linux-next until it
releases in 5.7 sometime in the late summer.
I think that's the maximal exposure we can do before it hits an
upstream, non-rc release and hope that whoever wants to complain, will
do so before then.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists