From: Segher Boessenkool <segher@kernel.crashing.org>
To: Balbir Singh <bsingharora@gmail.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
Jan Stancek <jstancek@redhat.com>,
Herton Krzesinski <hkrzesin@redhat.com>,
Artem Savkov <asavkov@redhat.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [bug] stack protector panics on v4.10-rc1+
Date: Tue, 24 Jan 2017 22:17:02 -0600 [thread overview]
Message-ID: <20170125041702.GM30284@gate.crashing.org> (raw)
In-Reply-To: <20170125035453.GA12855@localhost.localdomain>
On Wed, Jan 25, 2017 at 09:24:53AM +0530, Balbir Singh wrote:
> > So my inclination is to revert the powerpc stack protector code for
> > 4.10, and we can try again for 4.11 or 12.
>
> That makes sense. We then wait for the right gcc version? I guess we also
> push for per-task gaurd value as opposed to a global one?
Global value will work (with GCC 7) as-is. Per-task will require some
kernel work, but yeah you want it, that is why the options for that exist ;-)
You don't have to revert the current stack protector code; just condition it
on the relevant GCC flags (you will need to do that later anyway).
Segher
next prev parent reply other threads:[~2017-01-25 4:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <627000186.495731.1485210132000.JavaMail.zimbra@redhat.com>
2017-01-24 0:10 ` [bug] stack protector panics on v4.10-rc1+ Jan Stancek
2017-01-24 0:35 ` Tyrel Datwyler
2017-01-24 1:04 ` Segher Boessenkool
2017-01-24 3:41 ` Michael Ellerman
2017-01-24 4:09 ` Michael Ellerman
2017-01-25 3:54 ` Balbir Singh
2017-01-25 4:17 ` Segher Boessenkool [this message]
2017-01-26 7:05 ` Benjamin Herrenschmidt
2017-01-26 7:06 ` Benjamin Herrenschmidt
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=20170125041702.GM30284@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=asavkov@redhat.com \
--cc=bsingharora@gmail.com \
--cc=hkrzesin@redhat.com \
--cc=jstancek@redhat.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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).