From: Al Viro <viro@ZenIV.linux.org.uk>
To: Christoph Hellwig <hch@infradead.org>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
"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 15:54:27 +0000 [thread overview]
Message-ID: <20161104155427.GF19539@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20161104152223.GA1052@infradead.org>
On Fri, Nov 04, 2016 at 08:22:23AM -0700, Christoph Hellwig wrote:
> On Fri, Nov 04, 2016 at 03:18:11PM +0000, Al Viro wrote:
> > On Fri, Nov 04, 2016 at 03:24:24PM +0100, Sebastian Andrzej Siewior wrote:
> >
> > > Eventually Fedora and SUSE will migrate to PIE by default and by then we
> > > should cover all major distros so even Al should be affected unless he
> > > decides not to update or is using something else.
> >
> > That "something else" happens to be mostly Debian, actually.
>
> Debian is moving over to PIE already. Looks at this for example:
>
> https://lists.debian.org/debian-kernel/2016/10/msg00242.html
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.
next prev parent reply other threads:[~2016-11-04 15:54 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 [this message]
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=20161104155427.GF19539@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=ahferroin7@gmail.com \
--cc=ben@decadent.org.uk \
--cc=bigeasy@linutronix.de \
--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 \
/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).