From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Al Viro <viro@ZenIV.linux.org.uk>, Ben Hutchings <ben@decadent.org.uk>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-kernel@vger.kernel.org, Sven Joachim <svenjoac@gmx.de>,
Tomas Janousek <tomi@nomi.cz>, Joe Perches <joe@perches.com>,
Adam Borowski <kilobyte@angband.pl>,
Michal Marek <mmarek@suse.com>,
linux-kbuild@vger.kernel.org
Subject: Re: [PATCH 2/2] kbuild: add -fno-PIE
Date: Fri, 4 Nov 2016 07:37:02 -0400 [thread overview]
Message-ID: <adb64e4e-0745-c23c-2b8f-a67372b1d28f@gmail.com> (raw)
In-Reply-To: <20161104010811.GD19539@ZenIV.linux.org.uk>
On 2016-11-03 21:08, Al Viro wrote:
> On Thu, Nov 03, 2016 at 04:50:55PM -0600, Ben Hutchings wrote:
>> On Wed, 2016-11-02 at 18:20 +0100, Sebastian Andrzej Siewior wrote:
>>> Debian started to build the gcc with -fPIE by default so the kernel
>>> build ends before it starts properly with:
>>> |kernel/bounds.c:1:0: error: code model kernel does not support PIC mode
>>>
>>>
>>> Also add to KBUILD_AFLAGSi due to:
>>>
>>> |gcc -Wp,-MD,arch/x86/entry/vdso/vdso32/.note.o.d … -mfentry -DCC_USING_FENTRY … vdso/vdso32/note.S
>>> |arch/x86/entry/vdso/vdso32/note.S:1:0: sorry, unimplemented: -mfentry isn’t supported for 32-bit in c ombination with -fpic
>> [...]
>>
>> Unfortunately this isn't sufficient:
>>
>> Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong available but compiler is broken
>> /build/linux-4.9~rc3/Makefile:1069: recipe for target 'prepare-compiler-check' failed
>> make[5]: *** [prepare-compiler-check] Error 1
>>
>> scripts/gcc-x86_64-has-stack-protector.sh has its own list of options
>> which will need to include -fno-PIE.
>
> That shit should be fixed in debian; no amount of kbuild changes will help
> on bisect going back to a state prior to those. IOW, no matter what we
> do kernel-side, that fuckup by doku, balint, et.al. needs to be fixed in
> debian gcc package.
>
> Al, seriously disappointed by that mess - debian gcc packagers are generally
> clued enough to have known better. Reassigning bug reports in question
> from gcc-6 to linux is beyond stupid; Balint is either being deliberately
> obtuse, or geniunely unable to imagine that somebody might be using the
> compiler _not_ for debian package builds.
>
If it helps, you could point out that Gentoo's hardened profile's GCC
builds use PIE by default and have absolutely zero issues building the
Linux kernel without any special kernel patches to turn it off (and has
been doing so for years).
next prev parent reply other threads:[~2016-11-04 11:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-02 17:20 [PATCH 1/2] Documentation/HOWTO: Use a more recent gcc + binutils Sebastian Andrzej Siewior
2016-11-02 17:20 ` [PATCH 2/2] kbuild: add -fno-PIE Sebastian Andrzej Siewior
2016-11-03 22:50 ` Ben Hutchings
2016-11-04 1:08 ` Al Viro
2016-11-04 11:37 ` Austin S. Hemmelgarn [this message]
2016-11-04 14:24 ` Sebastian Andrzej Siewior
2016-11-04 14:39 ` Markus Trippelsdorf
2016-11-04 14:55 ` Austin S. Hemmelgarn
2016-11-04 14:47 ` Austin S. Hemmelgarn
2016-11-04 15:18 ` Al Viro
2016-11-04 15:22 ` Christoph Hellwig
2016-11-04 15:54 ` Al Viro
2016-11-04 15:58 ` Sebastian Andrzej Siewior
2016-11-04 16:10 ` Al Viro
2016-11-04 16:17 ` Sebastian Andrzej Siewior
2016-11-04 16:25 ` Adam Borowski
2016-11-02 18:52 ` [PATCH 1/2] Documentation/HOWTO: Use a more recent gcc + binutils Sven Joachim
2016-11-02 19:55 ` Borislav Petkov
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=adb64e4e-0745-c23c-2b8f-a67372b1d28f@gmail.com \
--to=ahferroin7@gmail.com \
--cc=ben@decadent.org.uk \
--cc=bigeasy@linutronix.de \
--cc=joe@perches.com \
--cc=kilobyte@angband.pl \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.com \
--cc=svenjoac@gmx.de \
--cc=tomi@nomi.cz \
--cc=viro@ZenIV.linux.org.uk \
/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.