diff options
author | Leonard Chan <leonardchan@google.com> | 2021-10-04 11:12:15 -0700 |
---|---|---|
committer | Leonard Chan <leonardchan@google.com> | 2021-10-04 13:14:20 -0700 |
commit | 993555beb8ff33aa35773af01cb3821ae45e6e39 (patch) | |
tree | 4116c56b0bdc04dc30b86847fbd4bf3a697f174b /llvm/lib/CodeGen/MachineFunction.cpp | |
parent | 30001af84ec5fa0c4f88da1df9c6682bdff44226 (diff) | |
download | llvm-993555beb8ff33aa35773af01cb3821ae45e6e39.zip llvm-993555beb8ff33aa35773af01cb3821ae45e6e39.tar.gz llvm-993555beb8ff33aa35773af01cb3821ae45e6e39.tar.bz2 |
[compiler-rt][scudo] Check for failing prctl call
A bunch of MTE tests like ./ScudoUnitTest-aarch64-Test/MemtagTest.StoreTags
can fail on aarch64-linux if the kernel doesn't support the tagged address ABI. It looks like
the call to prctl(PR_GET_TAGGED_ADDR_CTRL, 0, 0, 0, 0) can return -1, which
casted to an unsigned int and masked will return a value not equal to
PR_MTE_TCF_NONE, meaning systemDetectsMemoryTagFaultsTestOnly can return an incorrect value.
This updates the check to account for a failing prctl call.
Differential Revision: https://reviews.llvm.org/D110888
Diffstat (limited to 'llvm/lib/CodeGen/MachineFunction.cpp')
0 files changed, 0 insertions, 0 deletions