From: Florian Weimer <fweimer@redhat.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Cc: shenhan@google.com
Subject: Extend -fstack-protector-strong to cover calls with return slot
Date: Fri, 03 Jan 2014 13:15:00 -0000 [thread overview]
Message-ID: <52C6B807.1070203@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 378 bytes --]
This patch fixes a loophole in the -fstack-protector-strong protection.
If a function call uses the return slot optimization, the caller needs
stack protector instrumentation because the return slot is addressable.
Bootstrapped and regression-tested on x86_64-redhat-linux-gnu, with
C/C++/Java enabled. Okay for trunk?
--
Florian Weimer / Red Hat Product Security Team
[-- Attachment #2: ssp-strong-nrv.patch --]
[-- Type: text/x-patch, Size: 4221 bytes --]
gcc/
2014-01-03 Florian Weimer <fweimer@redhat.com>
* cfgexpand.c (call_with_return_slot_opt_p): New function.
(expand_used_vars): Emit stack protector instrumentation in strong
mode if call_with_return_slot_opt_p.
gcc/testsuite/
2014-01-03 Florian Weimer <fweimer@redhat.com>
* gcc.dg/fstack-protector-strong.c: Add coverage for named return
values.
* g++.dg/fstack-protector-strong.C: Likewise.
Index: gcc/cfgexpand.c
===================================================================
--- gcc/cfgexpand.c (revision 206311)
+++ gcc/cfgexpand.c (working copy)
@@ -1599,6 +1599,22 @@
return 0;
}
+/* Check if the basic block has a call which uses a return slot. */
+
+static bool
+call_with_return_slot_opt_p (basic_block bb)
+{
+ for (gimple_stmt_iterator gsi = gsi_start_bb (bb);
+ !gsi_end_p (gsi); gsi_next (&gsi))
+ {
+ gimple stmt = gsi_stmt (gsi);
+ if (gimple_code (stmt) == GIMPLE_CALL
+ && gimple_call_return_slot_opt_p (stmt))
+ return true;
+ }
+ return false;
+}
+
/* Expand all variables used in the function. */
static rtx
@@ -1669,22 +1685,35 @@
pointer_map_destroy (ssa_name_decls);
if (flag_stack_protect == SPCT_FLAG_STRONG)
- FOR_EACH_LOCAL_DECL (cfun, i, var)
- if (!is_global_var (var))
+ {
+ FOR_EACH_LOCAL_DECL (cfun, i, var)
+ if (!is_global_var (var))
+ {
+ tree var_type = TREE_TYPE (var);
+ /* Examine local referenced variables that have their
+ addresses taken, contain an array, or are arrays. */
+ if (TREE_CODE (var) == VAR_DECL
+ && (TREE_CODE (var_type) == ARRAY_TYPE
+ || TREE_ADDRESSABLE (var)
+ || (RECORD_OR_UNION_TYPE_P (var_type)
+ && record_or_union_type_has_array_p (var_type))))
+ {
+ gen_stack_protect_signal = true;
+ break;
+ }
+ }
+ /* The return slot introduces addressable local variables. */
+ if (!gen_stack_protect_signal)
{
- tree var_type = TREE_TYPE (var);
- /* Examine local referenced variables that have their addresses taken,
- contain an array, or are arrays. */
- if (TREE_CODE (var) == VAR_DECL
- && (TREE_CODE (var_type) == ARRAY_TYPE
- || TREE_ADDRESSABLE (var)
- || (RECORD_OR_UNION_TYPE_P (var_type)
- && record_or_union_type_has_array_p (var_type))))
+ basic_block bb;
+ FOR_ALL_BB_FN (bb, cfun)
{
- gen_stack_protect_signal = true;
- break;
+ gen_stack_protect_signal = call_with_return_slot_opt_p (bb);
+ if (gen_stack_protect_signal)
+ break;
}
}
+ }
/* At this point all variables on the local_decls with TREE_USED
set are not associated with any block scope. Lay them out. */
Index: gcc/testsuite/g++.dg/fstack-protector-strong.C
===================================================================
--- gcc/testsuite/g++.dg/fstack-protector-strong.C (revision 206311)
+++ gcc/testsuite/g++.dg/fstack-protector-strong.C (working copy)
@@ -32,4 +32,39 @@
return global_func (a);
}
-/* { dg-final { scan-assembler-times "stack_chk_fail" 2 } } */
+/* Frame addressed exposed through return slot. */
+
+struct B
+{
+ /* Discourage passing this struct in registers. */
+ int a1, a2, a3, a4, a5, a6, a7, a8, a9, a10;
+};
+
+B global_func ();
+void noop ();
+
+int foo3 ()
+{
+ return global_func ().a1;
+}
+
+int foo4 ()
+{
+ try {
+ noop ();
+ return 0;
+ } catch (...) {
+ return global_func ().a1;
+ }
+}
+
+int foo5 ()
+{
+ try {
+ return global_func ().a1;
+ } catch (...) {
+ return 0;
+ }
+}
+
+/* { dg-final { scan-assembler-times "stack_chk_fail" 5 } } */
Index: gcc/testsuite/gcc.dg/fstack-protector-strong.c
===================================================================
--- gcc/testsuite/gcc.dg/fstack-protector-strong.c (revision 206311)
+++ gcc/testsuite/gcc.dg/fstack-protector-strong.c (working copy)
@@ -131,4 +131,17 @@
return bb.three;
}
-/* { dg-final { scan-assembler-times "stack_chk_fail" 10 } } */
+struct B
+{
+ /* Discourage passing this struct in registers. */
+ int a1, a2, a3, a4, a5, a6, a7, a8, a9, a10;
+};
+
+struct B global3 (void);
+
+int foo11 ()
+{
+ return global3 ().a1;
+}
+
+/* { dg-final { scan-assembler-times "stack_chk_fail" 11 } } */
next reply other threads:[~2014-01-03 13:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-03 13:15 Florian Weimer [this message]
2014-01-03 18:57 ` Jakub Jelinek
2014-01-03 21:43 ` Florian Weimer
2014-01-07 12:51 ` Florian Weimer
2014-01-07 13:07 ` Jakub Jelinek
2014-01-07 13:27 ` Florian Weimer
2014-01-07 13:37 ` Jakub Jelinek
2014-01-08 14:57 ` Florian Weimer
2014-01-17 10:26 ` Florian Weimer
2014-02-03 9:05 ` [PATCH Ping] " Florian Weimer
2014-05-05 11:58 ` [PATCH Ping v2] " Florian Weimer
2014-05-09 6:26 ` Jeff Law
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=52C6B807.1070203@redhat.com \
--to=fweimer@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=shenhan@google.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).