Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750936AbdL3NPW (ORCPT ); Sat, 30 Dec 2017 08:15:22 -0500 Received: from twin.jikos.cz ([91.219.245.39]:56839 "EHLO twin.jikos.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750762AbdL3NPU (ORCPT ); Sat, 30 Dec 2017 08:15:20 -0500 Date: Sat, 30 Dec 2017 14:14:57 +0100 (CET) From: Jiri Kosina To: =?ISO-8859-15?Q?Toralf_F=F6rster?= cc: Alexander Tsoy , Andy Lutomirski , Linus Torvalds , stable , Linux Kernel , the arch/x86 maintainers , jpoimboe@redhat.com Subject: Re: 4.14.9 doesn't boot (regression) In-Reply-To: <755e371f-576c-419d-b8fe-66232e8de680@gmx.de> Message-ID: References: <33249a35-7d6a-f0f3-5a98-e6474f9366e3@gmx.de> <7A0A9B37-20FF-4B17-B4F5-D8B999269FC4@amacapital.net> <1514596414.28262.22.camel@tsoy.me> <755e371f-576c-419d-b8fe-66232e8de680@gmx.de> User-Agent: Alpine 2.00 (LRH 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-15 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1368 Lines: 38 On Sat, 30 Dec 2017, Toralf F?rster wrote: > 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. -fstack-check for kernel is never going to work properly. That option is purely for userspace, and assumes all the logic around 'stack guard gap' and the auto-growing semantics being in place; which is there for user stack VMA, but definitely not for kernel stack. It's probably the "hardened" flavor of your distro trying to push '-fstack-check' to everything it compiles; so I actually think the Makefile patch, sanitizing CFLAGS by force-disabling -fstack-check is exactly what we should be doing. Thanks, -- Jiri Kosina SUSE Labs