summaryrefslogtreecommitdiff
path: root/lib/scudo/standalone/fuchsia.cc
diff options
context:
space:
mode:
authorKostya Kortchinsky <kostyak@google.com>2019-06-18 17:41:17 +0000
committerKostya Kortchinsky <kostyak@google.com>2019-06-18 17:41:17 +0000
commit63696db5559d8d9fac828309c2799daebba721ff (patch)
treea3c19f83c86441fe07db2917ffa95aeb1770877f /lib/scudo/standalone/fuchsia.cc
parent7727012e5d946fd128274a41a4b159e990787ed2 (diff)
downloadcompiler-rt-63696db5559d8d9fac828309c2799daebba721ff.tar.gz
[scudo][standalone] Fuchsia related changes
Summary: Fuchsia wants to use mutexes with PI in the Scudo code, as opposed to our own implementation. This required making `lock` & `unlock` platform specific (as opposed to `wait` & `wake`) [code courtesy of John Grossman]. There is an additional flag required now for mappings as well: `ZX_VM_ALLOW_FAULTS`. Reviewers: morehouse, mcgrathr, eugenis, vitalybuka, hctim Reviewed By: morehouse Subscribers: delcypher, jfb, #sanitizers, llvm-commits Tags: #llvm, #sanitizers Differential Revision: https://reviews.llvm.org/D63435 git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@363705 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'lib/scudo/standalone/fuchsia.cc')
-rw-r--r--lib/scudo/standalone/fuchsia.cc32
1 files changed, 19 insertions, 13 deletions
diff --git a/lib/scudo/standalone/fuchsia.cc b/lib/scudo/standalone/fuchsia.cc
index e54563138..cf0323819 100644
--- a/lib/scudo/standalone/fuchsia.cc
+++ b/lib/scudo/standalone/fuchsia.cc
@@ -14,8 +14,10 @@
#include "mutex.h"
#include "string_utils.h"
-#include <limits.h> // for PAGE_SIZE
-#include <stdlib.h> // for getenv()
+#include <lib/sync/mutex.h> // for sync_mutex_t
+#include <limits.h> // for PAGE_SIZE
+#include <stdlib.h> // for getenv()
+#include <zircon/compiler.h>
#include <zircon/sanitizer.h>
#include <zircon/syscalls.h>
@@ -90,7 +92,8 @@ void *map(void *Addr, uptr Size, const char *Name, uptr Flags,
}
uintptr_t P;
- zx_vm_option_t MapFlags = ZX_VM_PERM_READ | ZX_VM_PERM_WRITE;
+ zx_vm_option_t MapFlags =
+ ZX_VM_PERM_READ | ZX_VM_PERM_WRITE | ZX_VM_ALLOW_FAULTS;
const uint64_t Offset =
Addr ? reinterpret_cast<uintptr_t>(Addr) - Data->VmarBase : 0;
if (Offset)
@@ -149,18 +152,21 @@ void releasePagesToOS(UNUSED uptr BaseAddress, uptr Offset, uptr Size,
const char *getEnv(const char *Name) { return getenv(Name); }
-void BlockingMutex::wait() {
- const zx_status_t Status =
- _zx_futex_wait(reinterpret_cast<zx_futex_t *>(OpaqueStorage), MtxSleeping,
- ZX_HANDLE_INVALID, ZX_TIME_INFINITE);
- if (Status != ZX_ERR_BAD_STATE)
- CHECK_EQ(Status, ZX_OK); // Normal race
+// Note: we need to flag these methods with __TA_NO_THREAD_SAFETY_ANALYSIS
+// because the Fuchsia implementation of sync_mutex_t has clang thread safety
+// annotations. Were we to apply proper capability annotations to the top level
+// BlockingMutex class itself, they would not be needed. As it stands, the
+// thread analysis thinks that we are locking the mutex and accidentally leaving
+// it locked on the way out.
+void BlockingMutex::lock() __TA_NO_THREAD_SAFETY_ANALYSIS {
+ // Size and alignment must be compatible between both types.
+ COMPILER_CHECK(sizeof(sync_mutex_t) <= sizeof(OpaqueStorage));
+ COMPILER_CHECK(!(alignof(decltype(OpaqueStorage)) % alignof(sync_mutex_t)));
+ sync_mutex_lock(reinterpret_cast<sync_mutex_t *>(OpaqueStorage));
}
-void BlockingMutex::wake() {
- const zx_status_t Status =
- _zx_futex_wake(reinterpret_cast<zx_futex_t *>(OpaqueStorage), 1);
- CHECK_EQ(Status, ZX_OK);
+void BlockingMutex::unlock() __TA_NO_THREAD_SAFETY_ANALYSIS {
+ sync_mutex_unlock(reinterpret_cast<sync_mutex_t *>(OpaqueStorage));
}
u64 getMonotonicTime() { return _zx_clock_get_monotonic(); }