From: hpa@zytor.com (H. Peter Anvin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] use -fstack-protector-strong
Date: Mon, 25 Nov 2013 15:16:54 -0800 [thread overview]
Message-ID: <5293DA66.6050902@zytor.com> (raw)
In-Reply-To: <20131125221400.GA11041@www.outflux.net>
On 11/25/2013 02:14 PM, Kees Cook wrote:
> Build the kernel with -fstack-protector-strong when it is available
> (gcc 4.9 and later). This increases the coverage of the stack protector
> without the heavy performance hit of -fstack-protector-all.
What is the difference between the various options?
-hpa
WARNING: multiple messages have this Message-ID (diff)
From: "H. Peter Anvin" <hpa@zytor.com>
To: Kees Cook <keescook@chromium.org>, linux-kernel@vger.kernel.org
Cc: Russell King <linux@arm.linux.org.uk>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
x86@kernel.org, Shawn Guo <shawn.guo@linaro.org>,
Olof Johansson <olofj@chromium.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] use -fstack-protector-strong
Date: Mon, 25 Nov 2013 15:16:54 -0800 [thread overview]
Message-ID: <5293DA66.6050902@zytor.com> (raw)
In-Reply-To: <20131125221400.GA11041@www.outflux.net>
On 11/25/2013 02:14 PM, Kees Cook wrote:
> Build the kernel with -fstack-protector-strong when it is available
> (gcc 4.9 and later). This increases the coverage of the stack protector
> without the heavy performance hit of -fstack-protector-all.
What is the difference between the various options?
-hpa
next prev parent reply other threads:[~2013-11-25 23:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 22:14 [PATCH] use -fstack-protector-strong Kees Cook
2013-11-25 22:14 ` Kees Cook
2013-11-25 23:16 ` H. Peter Anvin [this message]
2013-11-25 23:16 ` H. Peter Anvin
2013-11-25 23:43 ` Kees Cook
2013-11-25 23:43 ` Kees Cook
2013-11-26 4:21 ` Nicolas Pitre
2013-11-26 4:21 ` Nicolas Pitre
2013-11-26 11:19 ` Ingo Molnar
2013-11-26 11:19 ` Ingo Molnar
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=5293DA66.6050902@zytor.com \
--to=hpa@zytor.com \
--cc=linux-arm-kernel@lists.infradead.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 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.