mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexander Tsoy <alexander@tsoy.me>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Andy Lutomirski <luto@amacapital.net>,
	Dave Hansen <dave.hansen@intel.com>
Cc: "Toralf Förster" <toralf.foerster@gmx.de>,
	stable <stable@vger.kernel.org>,
	"Linux Kernel" <linux-kernel@vger.kernel.org>,
	"the arch/x86 maintainers" <x86@kernel.org>,
	"Josh Poimboeuf" <jpoimboe@redhat.com>
Subject: Re: 4.14.9 doesn't boot (regression)
Date: Sat, 30 Dec 2017 12:14:02 +0300	[thread overview]
Message-ID: <1514625242.2379.4.camel@tsoy.me> (raw)
In-Reply-To: <CA+55aFyJDzwih5yp6m=+NpKcJQhMD8OitTjh-+9FVOO_PmeqAw@mail.gmail.com>

В Пт, 29/12/2017 в 17:34 -0800, Linus Torvalds пишет:
> On Fri, Dec 29, 2017 at 5:00 PM, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> > 
> > Good. I was not feeling so happy about this bug report, but now I
> > can
> > firmly just blame the gentoo compiler for having some shit-for-
> > brains
> > "feature".
> 
> Looks like I can generate similar bad code with the F26 version of
> gcc, it's just not enabled by default.
> 
> So all gentoo did was change the default options.

Yes, and only in hardened profile, so most users don't have -fstack-
check by default. :)

> 
> I suspect we should just add a
> 
>     KBUILD_CFLAGS  += $(call cc-option,-fno-stack-check,)
> 
> somewhere to the main Makefile, just to make sure.
> 
> Maybe like the appended?
> 
> Toralf, Alexander, does this make things JustWork(tm) for you?

I can confirm that with your patch my gcc produces working kernel.

  reply	other threads:[~2017-12-30  9:14 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-29 11:14 Toralf Förster
2017-12-29 13:33 ` Sebastian Gottschall
2017-12-29 13:38   ` Toralf Förster
2017-12-29 15:29     ` Andy Shevchenko
2017-12-29 15:48 ` Alexander Tsoy
2017-12-29 15:52   ` Toralf Förster
2017-12-29 20:12 ` Linus Torvalds
2017-12-29 20:21   ` Ingo Molnar
2017-12-29 21:02   ` Toralf Förster
2017-12-29 21:17     ` Linus Torvalds
2017-12-29 21:39       ` Linus Torvalds
2017-12-29 22:04         ` Alexander Tsoy
2017-12-29 22:30       ` Toralf Förster
2017-12-29 22:53         ` Linus Torvalds
2017-12-29 23:14           ` Toralf Förster
2017-12-30  0:10           ` Andy Lutomirski
2017-12-30  1:00             ` Linus Torvalds
2017-12-30  1:34               ` Linus Torvalds
2017-12-30  9:14                 ` Alexander Tsoy [this message]
2017-12-30  9:21                   ` Toralf Förster
2017-12-30  1:13             ` Alexander Tsoy
2017-12-30 12:58               ` Toralf Förster
2017-12-30 13:14                 ` Jiri Kosina
2017-12-30  3:49             ` Josh Poimboeuf
2017-12-30  8:45               ` Alexander Tsoy
2017-12-30 17:09                 ` Josh Poimboeuf
2017-12-30 17:57                   ` Josh Poimboeuf
2017-12-30 22:03                     ` Alexander Tsoy
2017-12-30 22:16                       ` Josh Poimboeuf
2017-12-30  9:30               ` Toralf Förster
2017-12-30  8:32             ` Toralf Förster
2017-12-30  9:53           ` Jiri Kosina

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=1514625242.2379.4.camel@tsoy.me \
    --to=alexander@tsoy.me \
    --cc=dave.hansen@intel.com \
    --cc=jpoimboe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=stable@vger.kernel.org \
    --cc=toralf.foerster@gmx.de \
    --cc=torvalds@linux-foundation.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®