[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <755e371f-576c-419d-b8fe-66232e8de680@gmx.de>
Date: Sat, 30 Dec 2017 13:58:20 +0100
From: Toralf Förster <toralf.foerster@....de>
To: Alexander Tsoy <alexander@...y.me>,
Andy Lutomirski <luto@...capital.net>,
Linus Torvalds <torvalds@...ux-foundation.org>
Cc: stable <stable@...r.kernel.org>,
Linux Kernel <linux-kernel@...r.kernel.org>,
the arch/x86 maintainers <x86@...nel.org>,
jpoimboe@...hat.com
Subject: Re: 4.14.9 doesn't boot (regression)
On 12/30/2017 02:13 AM, Alexander Tsoy wrote:
> You are right, It's due to fstack-check enabled in gentoo's gcc spec.
> "-fstack-check=no" in KBUILD_CFLAGS fixed this problem for me. =/
This made the issue go away :
diff --git a/Makefile b/Makefile
index ac8c441866b7..11a12947c550 100644
--- a/Makefile
+++ b/Makefile
@@ -414,7 +414,7 @@ LINUXINCLUDE := \
KBUILD_AFLAGS := -D__ASSEMBLY__
KBUILD_CFLAGS := -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs \
- -fno-strict-aliasing -fno-common -fshort-wchar \
+ -fno-strict-aliasing -fno-common -fshort-wchar -fstack-check=no \
-Werror-implicit-function-declaration \
-Wno-format-security \
-std=gnu89
But this doesn't solve the root cause, right ? So if the root cause is "Gentoo hardened GCC is broken" please just let me know this - FWIW I'm in #gentoo-dev on freenode.
--
Toralf
PGP C4EACDDE 0076E94E
Powered by blists - more mailing lists