diff options
author | ChiaHungDuan <chiahungduan@google.com> | 2023-10-05 11:35:41 -0700 |
---|---|---|
committer | GitHub <noreply@github.com> | 2023-10-05 11:35:41 -0700 |
commit | ea2036e1e56b720d7da8d46f62263ba46c126522 (patch) | |
tree | 720600afc7ba2252f30e827c9c9e7393c756410e /llvm/lib/Analysis/ModuleSummaryAnalysis.cpp | |
parent | 9bbd2bf654634cd95dd0be7948ec8402c3c76e1e (diff) | |
download | llvm-ea2036e1e56b720d7da8d46f62263ba46c126522.zip llvm-ea2036e1e56b720d7da8d46f62263ba46c126522.tar.gz llvm-ea2036e1e56b720d7da8d46f62263ba46c126522.tar.bz2 |
[scudo] Fix the use of ASSERT_CAPABILITY in TSD (#68273)
In getCache()/getQuarantineCache(), they return a reference to variable
guarded by a mutex. After #67776, thread-safey analysis checks if a
variable return by reference has the lock held. The ASSERT_CAPABILITY
only claims after calling that function, the lock will be held. But not
asserting that the lock is held *before* calling that function.
In the patch, we switch to use REQUIRES() and assertLocked() to mark the
code paths. Also remove the misused ASSERT_CAPABILITY.
Fixes #67795, #67796
Diffstat (limited to 'llvm/lib/Analysis/ModuleSummaryAnalysis.cpp')
0 files changed, 0 insertions, 0 deletions