All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adam Borowski <kilobyte@angband.pl>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
	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>,
	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 17:25:04 +0100	[thread overview]
Message-ID: <20161104162504.GA7375@angband.pl> (raw)
In-Reply-To: <20161104155855.diyclit55eay6gxk@linutronix.de>

On Fri, Nov 04, 2016 at 04:58:55PM +0100, Sebastian Andrzej Siewior wrote:
> 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.

As you guys don't want Gentooish attempts to check if gcc is compiling the
kernel, what about making/requesting a wrapper that calls gcc with the
appropriate options (-fno-PIE and whatever is needed for fstack protector)?

This would require manually appending CC=the-wrapper to make but would allow
bisects.  And come on, any solution with no bisects is rather ridiculous.


Meow!
-- 
A MAP07 (Dead Simple) raspberry tincture recipe: 0.5l 95% alcohol, 1kg
raspberries, 0.4kg sugar; put into a big jar for 1 month.  Filter out and
throw away the fruits (can dump them into a cake, etc), let the drink age
at least 3-6 months.

  parent reply	other threads:[~2016-11-04 16:25 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
2016-11-04 16:10                   ` Al Viro
2016-11-04 16:17                     ` Sebastian Andrzej Siewior
2016-11-04 16:25                   ` Adam Borowski [this message]
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=20161104162504.GA7375@angband.pl \
    --to=kilobyte@angband.pl \
    --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=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.