From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Christoph Hellwig <hch@infradead.org>,
"Austin S. Hemmelgarn" <ahferroin7@gmail.com>,
Ben Hutchings <ben@decadent.org.uk>,
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, doko@debian.org
Subject: Re: [PATCH 2/2] kbuild: add -fno-PIE
Date: Fri, 4 Nov 2016 16:58:55 +0100 [thread overview]
Message-ID: <20161104155855.diyclit55eay6gxk@linutronix.de> (raw)
In-Reply-To: <20161104155427.GF19539@ZenIV.linux.org.uk>
On 2016-11-04 15:54:27 [+0000], Al Viro wrote:
> Christoph, would you mind rereading what I posted upthread? I *am* aware of
> that clusterfuck, including the Balint's charming games with the reassignments,
> etc. Directly affected by the whole mess, actually.
Al, I am re-doing the patch with a runtime check for -fno-PIE and
tagging it stable and looking after Ben's fstack protector thingy.
This should allow you to compile maintained stable kernels but it won't
allow you to bisect to prior versions.
I don't see any other way around it.
Sebastian
next prev parent reply other threads:[~2016-11-04 15:59 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
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 [this message]
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=20161104155855.diyclit55eay6gxk@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=ahferroin7@gmail.com \
--cc=ben@decadent.org.uk \
--cc=doko@debian.org \
--cc=hch@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).