[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=whmeBkyu3iS_s-yk0=t3GEoW3sQb-wJFHKykOjG=iQVFw@mail.gmail.com>
Date: Mon, 2 Jan 2023 18:13:09 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Guenter Roeck <linux@...ck-us.net>
Cc: "Jason A. Donenfeld" <Jason@...c4.com>,
Yoshinori Sato <ysato@...rs.sourceforge.jp>,
Rich Felker <dalias@...c.org>, Arnd Bergmann <arnd@...db.de>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Masahiro Yamada <masahiroy@...nel.org>,
Palmer Dabbelt <palmer@...osinc.com>,
Ard Biesheuvel <ardb@...nel.org>
Subject: Re: Linux 6.2-rc2
On Mon, Jan 2, 2023 at 5:45 PM Guenter Roeck <linux@...ck-us.net> wrote:
>
> ... and reverting commit 99cb0d917ff indeed fixes the problem.
Hmm. My gut feel is that this just exposes some bug in binutils.
That said, maybe that commit should not have added its own /DISCARDS/
thing, and instead just added that "*(.note.GNU-stack)" to the general
/DISCARDS/ thing that is defined by the
#define DISCARDS ..
a little bit later, so that we only end up with one single DISCARD
list. Something like this (broken patch on purpose):
--- a/include/asm-generic/vmlinux.lds.h
+++ b/include/asm-generic/vmlinux.lds.h
@@ -897,5 +897,4 @@
*/
#define NOTES \
- /DISCARD/ : { *(.note.GNU-stack) } \
.notes : AT(ADDR(.notes) - LOAD_OFFSET) { \
BOUNDED_SECTION_BY(.note.*, _notes) \
@@ -1016,4 +1015,5 @@
#define DISCARDS \
/DISCARD/ : { \
+ *(.note.GNU-stack) \
EXIT_DISCARDS \
EXIT_CALL \
But maybe that DISCARDS macrop ends up being used too late?
It really shouldn't matter, but here we are, with a build problem with
some random old binutils on an odd platform..
Linus
Powered by blists - more mailing lists