From: Borislav Petkov <bp@alien8.de>
To: Arvind Sankar <nivedita@alum.mit.edu>, "H. Peter Anvin" <hpa@zytor.com>
Cc: Kees Cook <keescook@chromium.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
Thomas Lendacky <Thomas.Lendacky@amd.com>,
Mauro Rossi <issor.oruam@gmail.com>, Michael Matz <matz@suse.de>
Subject: Re: [PATCH v3] x86/vmlinux: Fix vmlinux.lds.S with pre-2.23 binutils
Date: Wed, 15 Jan 2020 13:24:58 +0100 [thread overview]
Message-ID: <20200115122458.GB20975@zn.tnic> (raw)
In-Reply-To: <20200115002131.GA3258770@rani.riverdale.lan>
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
next prev parent reply other threads:[~2020-01-15 12:25 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 20:23 [PATCH] x86/tools/relocs: Add _etext and __end_of_kernel_reserve to S_REL Arvind Sankar
2020-01-10 20:38 ` Borislav Petkov
2020-01-10 20:50 ` Arvind Sankar
2020-01-10 21:50 ` [PATCH v2] " Arvind Sankar
2020-01-10 21:52 ` Arvind Sankar
2020-01-11 13:02 ` [PATCH] " Borislav Petkov
2020-01-11 17:20 ` Arvind Sankar
2020-01-11 17:32 ` Arvind Sankar
2020-01-13 13:43 ` Borislav Petkov
2020-01-13 16:13 ` Arvind Sankar
2020-01-13 16:38 ` Borislav Petkov
2020-01-13 17:59 ` Arvind Sankar
2020-01-13 18:08 ` Borislav Petkov
2020-01-14 4:17 ` Arvind Sankar
2020-01-14 11:25 ` Borislav Petkov
2020-01-14 16:32 ` Arvind Sankar
2020-01-14 4:08 ` Arvind Sankar
2020-01-13 19:53 ` [PATCH v3] x86/vmlinux: Fix vmlinux.lds.S with pre-2.23 binutils Arvind Sankar
2020-01-13 21:46 ` Tom Lendacky
2020-01-13 23:06 ` Arvind Sankar
2020-01-14 1:53 ` Kees Cook
2020-01-14 1:57 ` H. Peter Anvin
2020-01-14 2:20 ` Kees Cook
2020-01-14 3:58 ` Arvind Sankar
2020-01-14 5:05 ` hpa
2020-01-14 16:51 ` Borislav Petkov
2020-01-14 21:50 ` hpa
2020-01-15 0:21 ` Arvind Sankar
2020-01-15 12:24 ` Borislav Petkov [this message]
2020-03-16 16:02 ` [PATCH] Documentation/changes: Raise minimum supported binutils version to 2.23 Borislav Petkov
2020-03-16 20:54 ` Kees Cook
2020-03-23 20:44 ` Jason A. Donenfeld
2020-03-23 20:51 ` Kees Cook
2020-03-23 21:11 ` Jason A. Donenfeld
2020-03-25 17:33 ` David Laight
2020-03-24 9:02 ` Masahiro Yamada
2020-03-24 9:12 ` Masahiro Yamada
2020-03-24 15:38 ` Arvind Sankar
2020-03-24 17:31 ` Masahiro Yamada
2020-03-24 21:36 ` Arvind Sankar
2020-03-24 9:14 ` Borislav Petkov
2020-03-24 9:40 ` Masahiro Yamada
2020-03-24 12:00 ` Borislav Petkov
2020-03-24 16:22 ` Jason A. Donenfeld
2020-03-24 16:28 ` Borislav Petkov
2020-03-24 16:37 ` Linus Torvalds
2020-03-24 16:48 ` Borislav Petkov
2020-03-24 21:42 ` Arvind Sankar
2020-03-24 22:01 ` Arvind Sankar
2020-03-24 22:14 ` Linus Torvalds
2020-03-24 23:49 ` Arvind Sankar
2020-03-24 17:53 ` Kees Cook
2020-03-23 20:50 ` [PATCH] Documentation/changes: Raise minimum supported binutilsa " Nick Desaulniers
2020-01-13 23:38 ` [PATCH] x86/tools/relocs: Add _etext and __end_of_kernel_reserve to S_REL Arvind Sankar
2020-01-10 20:56 ` Kees Cook
[not found] ` <CAEQFVGa4fksPRtiLtBckSgbJY_JSHr07hoy5+5w-pAYym16YVg@mail.gmail.com>
2020-01-11 19:40 ` Fwd: " Mauro Rossi
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=20200115122458.GB20975@zn.tnic \
--to=bp@alien8.de \
--cc=Thomas.Lendacky@amd.com \
--cc=hpa@zytor.com \
--cc=issor.oruam@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matz@suse.de \
--cc=mingo@redhat.com \
--cc=nivedita@alum.mit.edu \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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 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.