| commit | 24496fe851268eec3994489a772842484376507d | |
| author | Daniele Buono <dbuono@linux.vnet.ibm.com> | |
| Fri, 4 Dec 2020 23:06:13 +0000 (4 18:06 -0500) | ||
| committer | Paolo Bonzini <pbonzini@redhat.com> | |
| Sat, 2 Jan 2021 20:03:36 +0000 (2 21:03 +0100) | ||
| tree | 28e15b3013593d86f3103d4863c30d243305b9ad | treesnapshot (tar.gz zip) |
| parent | c905a3680dc1dae044ea6b9aaf9f0482e5ebf63c | commitdiff |
check-block: enable iotests with cfi-icall
cfi-icall is a form of Control-Flow Integrity for indirect function
calls implemented by llvm. It is enabled with a -fsanitize flag.
iotests are currently disabled when -fsanitize options is used, with the
exception of SafeStack.
This patch implements a generic filtering mechanism to allow iotests
with a set of known-to-be-safe -fsanitize option. Then marks SafeStack
and the new options used for cfi-icall safe for iotests
Signed-off-by: Daniele Buono <dbuono@linux.vnet.ibm.com>
Message-Id: <20201204230615.2392-4-dbuono@linux.vnet.ibm.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
cfi-icall is a form of Control-Flow Integrity for indirect function
calls implemented by llvm. It is enabled with a -fsanitize flag.
iotests are currently disabled when -fsanitize options is used, with the
exception of SafeStack.
This patch implements a generic filtering mechanism to allow iotests
with a set of known-to-be-safe -fsanitize option. Then marks SafeStack
and the new options used for cfi-icall safe for iotests
Signed-off-by: Daniele Buono <dbuono@linux.vnet.ibm.com>
Message-Id: <20201204230615.2392-4-dbuono@linux.vnet.ibm.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
| tests/check-block.sh | diffblobblamehistory |