|author||Arjan van de Ven <firstname.lastname@example.org>||2008-04-18 06:16:45 -0700|
|committer||Thomas Gleixner <email@example.com>||2008-05-26 16:15:33 +0200|
stackprotector: turn not having the right gcc into a #warning
If the user selects the stack-protector config option, but does not have a gcc that has the right bits enabled (for example because it isn't build with a glibc that supports TLS, as is common for cross-compilers, but also because it may be too old), then the runtime test fails right now. This patch adds a warning message for this scenario. This warning accomplishes two goals 1) the user is informed that the security option he selective isn't available 2) the user is suggested to turn of the CONFIG option that won't work for him, and would make the runtime test fail anyway. Signed-off-by: Arjan van de Ven <firstname.lastname@example.org> Signed-off-by: Ingo Molnar <email@example.com> Signed-off-by: Thomas Gleixner <firstname.lastname@example.org>
Diffstat (limited to 'kernel/panic.c')
1 files changed, 3 insertions, 0 deletions
diff --git a/kernel/panic.c b/kernel/panic.c
index 866be9b72e4..6729e3f4ebc 100644
@@ -325,6 +325,9 @@ EXPORT_SYMBOL(warn_on_slowpath);
+#warning You have selected the CONFIG_CC_STACKPROTECTOR option, but the gcc used does not support this.
static unsigned long __stack_check_testing;
* Self test function for the stack-protector feature.