From: Segher Boessenkool <segher@kernel.crashing.org>
To: Christophe LEROY <christophe.leroy@c-s.fr>
Cc: Christian Kujau <lists@nerdbynature.de>,
Benjamin Herrenschmidt <benh@au1.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: bootx_init.c:88: undefined reference to `__stack_chk_fail_local'
Date: Wed, 11 Jan 2017 16:54:41 -0600 [thread overview]
Message-ID: <20170111225440.GQ28613@gate.crashing.org> (raw)
In-Reply-To: <d0e56084-49d7-2486-c2a6-de146331d1c7@c-s.fr>
On Tue, Jan 10, 2017 at 07:26:15AM +0100, Christophe LEROY wrote:
> >Maybe ppc32 is not supposed to be built with CC_STACKPROTECTOR ?
>
> Indeed, the latest versions of GCC don't use anymore the global variable
> __stack_chk_guard as canary value, but a value stored at -0x7008(r2).
> This is not compatible with the current implementation of the kernel
> with uses r2 as a pointeur to current task struct.
> So until we fix it, I don't think CC_STACKPROTECTOR is usable on PPC
> with modern versions of GCC.
I still wonder what changed. Nothing relevant has changed for ten years
or whatever as far as I see; unless it is just the -fstack-protector-strong
that makes it fail now. Curious.
Segher
next prev parent reply other threads:[~2017-01-11 22:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-03 15:25 bootx_init.c:88: undefined reference to `__stack_chk_fail_local' Christian Kujau
2017-01-03 19:20 ` Christian Kujau
2017-01-03 22:50 ` Benjamin Herrenschmidt
2017-01-03 22:57 ` Christian Kujau
2017-01-04 8:23 ` Christophe LEROY
2017-01-04 8:40 ` Segher Boessenkool
2017-01-04 7:32 ` Christophe LEROY
2017-01-04 15:22 ` Christian Kujau
2017-01-04 18:33 ` Christian Kujau
2017-01-10 2:11 ` Christian Kujau
2017-01-10 4:32 ` Benjamin Herrenschmidt
2017-01-10 6:12 ` Christophe LEROY
2017-01-10 18:46 ` Christian Kujau
2017-01-10 6:26 ` Christophe LEROY
2017-01-11 22:54 ` Segher Boessenkool [this message]
2017-01-12 7:52 ` Christophe LEROY
2017-01-12 14:42 ` Christophe LEROY
2017-01-12 15:20 ` Benjamin Herrenschmidt
2017-01-12 18:07 ` Segher Boessenkool
2017-01-13 12:15 ` Christophe LEROY
2017-01-13 12:23 ` David Laight
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=20170111225440.GQ28613@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=benh@au1.ibm.com \
--cc=christophe.leroy@c-s.fr \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lists@nerdbynature.de \
/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).