From: Segher Boessenkool <segher@kernel.crashing.org>
To: Christophe Leroy <christophe.leroy@c-s.fr>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Michael Ellerman <mpe@ellerman.id.au>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] powerpc/32: stack protector: change the canary value per task
Date: Mon, 17 Sep 2018 11:49:11 -0500 [thread overview]
Message-ID: <20180917164911.GK23155@gate.crashing.org> (raw)
In-Reply-To: <7bd67c4ccdd202f2125b7fc0ed0332d0d020690b.1537186089.git.christophe.leroy@c-s.fr>
On Mon, Sep 17, 2018 at 12:15:08PM +0000, Christophe Leroy wrote:
> I would have liked to use -mstack-protector-guard=tls -mstack-protector-guard-reg=r2
> -mstack-protector-guard-offset=offsetof(struct task_struct, stack_canary) but I have
> not found how set the value of offsetof(struct task_struct, stack_canary) in Makefile.
By far the easiest is to have the canary at a fixed offset from r2.
Segher
next prev parent reply other threads:[~2018-09-17 16:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-17 12:15 [PATCH 1/2] powerpc: initial stack protector (-fstack-protector) support Christophe Leroy
2018-09-17 12:15 ` [PATCH 2/2] powerpc/32: stack protector: change the canary value per task Christophe Leroy
2018-09-17 16:49 ` Segher Boessenkool [this message]
2018-09-17 16:21 ` [PATCH 1/2] powerpc: initial stack protector (-fstack-protector) support kbuild test robot
2018-09-17 16:46 ` Segher Boessenkool
-- strict thread matches above, loose matches on Subject: below --
2016-09-30 14:26 [PATCH 0/2] powerpc: " Christophe Leroy
2016-09-30 14:27 ` [PATCH 2/2] powerpc/32: stack protector: change the canary value per task Christophe Leroy
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=20180917164911.GK23155@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=benh@kernel.crashing.org \
--cc=christophe.leroy@c-s.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
/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).