[gcc(refs/users/aoliva/heads/testme)] hardcfr: prevent deferred sets of visited bitmap

Alexandre Oliva aoliva@gcc.gnu.org
Fri Jun 9 08:07:08 GMT 2023


https://gcc.gnu.org/g:0e2a8d05cd6f6103e9d9746d6a3e61f84030d299

commit 0e2a8d05cd6f6103e9d9746d6a3e61f84030d299
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Thu Jun 8 01:35:23 2023 -0300

    hardcfr: prevent deferred sets of visited bitmap
    
    Make bitmap sets volatile-ish, preventing deferral and likely
    combinations.
    
    
    for  gcc/ChangeLog
    
            * gimple-harden-control-flow.cc
            (rt_bb_visited::rt_bb_visited): Move optimization barrier...
            (rt_bb_visited::vset): ... here.

Diff:
---
 gcc/gimple-harden-control-flow.cc | 48 ++++++++++++++++++++++++---------------
 1 file changed, 30 insertions(+), 18 deletions(-)

diff --git a/gcc/gimple-harden-control-flow.cc b/gcc/gimple-harden-control-flow.cc
index 53717a652ca..3e6fe2db479 100644
--- a/gcc/gimple-harden-control-flow.cc
+++ b/gcc/gimple-harden-control-flow.cc
@@ -545,6 +545,36 @@ class rt_bb_visited
     gassign *vstore = gimple_build_assign (unshare_expr (setme), temp);
     gimple_seq_add_stmt (&seq, vstore);
 
+    /* Prevent stores into visited from being deferred, forcing
+       subsequent bitsets to reload the word rather than reusing
+       values already in register.  The purpose is threefold: make the
+       bitset get to memory in this block, so that control flow
+       attacks in functions called in this block don't easily bypass
+       the bitset; prevent the bitset word from being retained in a
+       register across blocks, which could, in an attack scenario,
+       make a later block set more than one bit; and prevent hoisting
+       or sinking loads or stores of bitset words out of loops or even
+       throughout functions, which could significantly weaken the
+       verification.  This is equivalent to making the bitsetting
+       volatile within the function body, but without changing its
+       type; making the bitset volatile would make inline checking far
+       less optimizable for no reason.  */
+    vec<tree, va_gc> *inputs = NULL;
+    vec<tree, va_gc> *outputs = NULL;
+    vec_safe_push (outputs,
+		   build_tree_list
+		   (build_tree_list
+		    (NULL_TREE, build_string (2, "=m")),
+		    visited));
+    vec_safe_push (inputs,
+		   build_tree_list
+		   (build_tree_list
+		    (NULL_TREE, build_string (1, "m")),
+		    visited));
+    gasm *stabilize = gimple_build_asm_vec ("", inputs, outputs,
+					    NULL, NULL);
+    gimple_seq_add_stmt (&seq, stabilize);
+
     return seq;
   }
 
@@ -615,24 +645,6 @@ public:
     tree visited_type = vtype ();
     visited = create_tmp_var (visited_type, ".cfrvisited");
 
-    /* Prevent stores into visited from being used to optimize the
-       control flow redundancy checks. asm ("" : "+m" (visited)); */
-    vec<tree, va_gc> *inputs = NULL;
-    vec<tree, va_gc> *outputs = NULL;
-    vec_safe_push (outputs,
-		   build_tree_list
-		   (build_tree_list
-		    (NULL_TREE, build_string (2, "=m")),
-		    visited));
-    vec_safe_push (inputs,
-		   build_tree_list
-		   (build_tree_list
-		    (NULL_TREE, build_string (1, "m")),
-		    visited));
-    gasm *detach = gimple_build_asm_vec ("", inputs, outputs,
-					 NULL, NULL);
-    gimple_seq_add_stmt (&ckseq, detach);
-
     if (nblocks - NUM_FIXED_BLOCKS > blknum (param_hardcfr_max_inline_blocks)
 	|| checkpoints > 1)
       {


More information about the Gcc-cvs mailing list