From: Jean Delvare <jdelvare@suse.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Ingo Molnar <mingo@redhat.com>,
Arjan van de Ven <arjan@linux.intel.com>,
Andi Kleen <andi@firstfloor.org>
Subject: [PATCH] CONFIG_CC_STACKPROTECTOR is no longer experimental
Date: Fri, 06 Jul 2012 16:08:25 +0200 [thread overview]
Message-ID: <1341583705.4655.18.camel@amber.site> (raw)
This feature has been around for over 5 years now, so I presume it is
no longer considered experimental.
Signed-off-by: Jean Delvare <jdelvare@suse.de>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Arjan van de Ven <arjan@linux.intel.com>
Cc: Andi Kleen <andi@firstfloor.org>
---
Or is there any reason to still consider this an experimental feature?
arch/x86/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- linux-3.5-rc5.orig/arch/x86/Kconfig 2012-06-05 16:22:58.000000000 +0200
+++ linux-3.5-rc5/arch/x86/Kconfig 2012-07-06 15:32:55.660276577 +0200
@@ -1525,7 +1525,7 @@ config SECCOMP
If unsure, say Y. Only embedded should say N here.
config CC_STACKPROTECTOR
- bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
+ bool "Enable -fstack-protector buffer overflow detection"
---help---
This option turns on the -fstack-protector GCC feature. This
feature puts, at the beginning of functions, a canary value on
--
Jean Delvare
Suse L3
next reply other threads:[~2012-07-06 14:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 14:08 Jean Delvare [this message]
2012-07-06 17:23 ` [PATCH] CONFIG_CC_STACKPROTECTOR is no longer experimental Randy Dunlap
2012-07-06 17:57 ` Jean Delvare
2012-07-06 17:58 ` Arjan van de Ven
2012-07-06 20:19 ` Paul Bolle
2012-07-09 7:56 ` Jean Delvare
2012-07-09 11:50 ` Jean Delvare
2012-07-09 13:11 ` Arjan van de Ven
2012-07-09 12:08 ` [tip:x86/urgent] x86: CONFIG_CC_STACKPROTECTOR= y " tip-bot for Jean Delvare
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=1341583705.4655.18.camel@amber.site \
--to=jdelvare@suse.de \
--cc=andi@firstfloor.org \
--cc=arjan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
/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.