aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Object/WasmObjectFile.cpp
diff options
context:
space:
mode:
authorKostya Kortchinsky <kostyak@google.com>2018-01-23 23:07:42 +0000
committerKostya Kortchinsky <kostyak@google.com>2018-01-23 23:07:42 +0000
commit1ebebde8b7b9f9636bc0d8556a2a1903ef3b7e88 (patch)
treec2543e49f1bafb04539590405d6ab253fbfb9a9b /llvm/lib/Object/WasmObjectFile.cpp
parentcbce2f02e9df04a1f7f292c4a2b8b50321f14fae (diff)
downloadllvm-1ebebde8b7b9f9636bc0d8556a2a1903ef3b7e88.zip
llvm-1ebebde8b7b9f9636bc0d8556a2a1903ef3b7e88.tar.gz
llvm-1ebebde8b7b9f9636bc0d8556a2a1903ef3b7e88.tar.bz2
[scudo] Allow for weak hooks, gated by a define
Summary: Hooks in the allocation & deallocation paths can be a security risk (see for an example https://scarybeastsecurity.blogspot.com/2016/11/0day-exploit-advancing-exploitation.html which used the glibc's __free_hook to complete exploitation). But some users have expressed a need for them, even if only for tests and memory benchmarks. So allow for `__sanitizer_malloc_hook` & `__sanitizer_free_hook` to be called if defined, and gate them behind a global define `SCUDO_CAN_USE_HOOKS` defaulting to 0. Reviewers: alekseyshl Reviewed By: alekseyshl Subscribers: #sanitizers, llvm-commits Differential Revision: https://reviews.llvm.org/D42430 llvm-svn: 323278
Diffstat (limited to 'llvm/lib/Object/WasmObjectFile.cpp')
0 files changed, 0 insertions, 0 deletions