| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
[GWP-ASan] Fuchsia specific mapping & utilities functions This CL introduces the Fuchsia versions of the existing platform specific functions. For Fuchsia, we need to track the VMAR (https://fuchsia.dev/fuchsia-src/reference/kernel_objects/vm_address_region) of the Guarded Pool mapping, and for this purpose I added some platform specific data structure that remains empty on POSIX platforms. getThreadID is not super useful for Fuchsia so it's just left as a stub for now. While testing the changes in my Fuchsia tree, I realized that guarded_pool_allocator_tls.h should have closed the namespace before including GWP_ASAN_PLATFORM_TLS_HEADER, otherwise drama ensues. This was tested in g3, upstream LLVM, and Fuchsia (with local changes). Differential Revision: https://reviews.llvm.org/D90483 | 5 年前 | |
[GWP-ASan] IWYU & clang-format Run an IWYU pass and clang-format GWP-ASan code. Reviewed By: eugenis, mcgrathr Differential Revision: https://reviews.llvm.org/D92688 | 5 年前 | |
[gwp_asan] Use zx_system_get_page_size() on Fuchsia Fuchsia is migrating to a variable page size. Reviewed By: hctim Differential Revision: https://reviews.llvm.org/D95920 | 5 年前 | |
[GWP-ASan] Fuchsia specific mapping & utilities functions This CL introduces the Fuchsia versions of the existing platform specific functions. For Fuchsia, we need to track the VMAR (https://fuchsia.dev/fuchsia-src/reference/kernel_objects/vm_address_region) of the Guarded Pool mapping, and for this purpose I added some platform specific data structure that remains empty on POSIX platforms. getThreadID is not super useful for Fuchsia so it's just left as a stub for now. While testing the changes in my Fuchsia tree, I realized that guarded_pool_allocator_tls.h should have closed the namespace before including GWP_ASAN_PLATFORM_TLS_HEADER, otherwise drama ensues. This was tested in g3, upstream LLVM, and Fuchsia (with local changes). Differential Revision: https://reviews.llvm.org/D90483 | 5 年前 | |
[GWP-ASan] Fix atfork handlers being installed multiple times in tests We incorrectly install the atfork handlers multiple times in the test harness, tracked down to the default parameter used by CheckLateInitIsOK. This manifested in a hang if running the tests with --gtest_repeat={>=2} as the atfork handler ran multiple times, causing double-lock and double-unlock, which on my machine hung. Add a check-fail for this case as well to prevent this from happening again (it was difficult to track down and is an easy mistake to make). Differential Revision: https://reviews.llvm.org/D139731 | 3 年前 | |
[GWP-ASan] Fuchsia specific mapping & utilities functions This CL introduces the Fuchsia versions of the existing platform specific functions. For Fuchsia, we need to track the VMAR (https://fuchsia.dev/fuchsia-src/reference/kernel_objects/vm_address_region) of the Guarded Pool mapping, and for this purpose I added some platform specific data structure that remains empty on POSIX platforms. getThreadID is not super useful for Fuchsia so it's just left as a stub for now. While testing the changes in my Fuchsia tree, I realized that guarded_pool_allocator_tls.h should have closed the namespace before including GWP_ASAN_PLATFORM_TLS_HEADER, otherwise drama ensues. This was tested in g3, upstream LLVM, and Fuchsia (with local changes). Differential Revision: https://reviews.llvm.org/D90483 | 5 年前 | |
[GWP-ASan] Fuchsia specific mapping & utilities functions This CL introduces the Fuchsia versions of the existing platform specific functions. For Fuchsia, we need to track the VMAR (https://fuchsia.dev/fuchsia-src/reference/kernel_objects/vm_address_region) of the Guarded Pool mapping, and for this purpose I added some platform specific data structure that remains empty on POSIX platforms. getThreadID is not super useful for Fuchsia so it's just left as a stub for now. While testing the changes in my Fuchsia tree, I realized that guarded_pool_allocator_tls.h should have closed the namespace before including GWP_ASAN_PLATFORM_TLS_HEADER, otherwise drama ensues. This was tested in g3, upstream LLVM, and Fuchsia (with local changes). Differential Revision: https://reviews.llvm.org/D90483 | 5 年前 | |
[GWP-ASan] Add mutexes for Fuchsia Mitch expressed a preference to not have #ifdefs in platform agnostic code, this change tries to accomodate this. I am not attached to the method this CL proposes, so if anyone has a suggestion, I am open. We move the platform specific member of the mutex into its own platform specific class that the main Mutex class inherits from. Functions are implemented in their respective platform specific compilation units. For Fuchsia, we use the sync APIs, as those are also the ones being used in Scudo. Differential Revision: https://reviews.llvm.org/D90351 | 5 年前 | |
[GWP-ASan] Add mutexes for Fuchsia Mitch expressed a preference to not have #ifdefs in platform agnostic code, this change tries to accomodate this. I am not attached to the method this CL proposes, so if anyone has a suggestion, I am open. We move the platform specific member of the mutex into its own platform specific class that the main Mutex class inherits from. Functions are implemented in their respective platform specific compilation units. For Fuchsia, we use the sync APIs, as those are also the ones being used in Scudo. Differential Revision: https://reviews.llvm.org/D90351 | 5 年前 | |
Attempt to fix 'mutex.h' not found when building mutex_posix. llvm-svn: 362149 | 6 年前 | |
[GWP-ASan] Add mutexes for Fuchsia Mitch expressed a preference to not have #ifdefs in platform agnostic code, this change tries to accomodate this. I am not attached to the method this CL proposes, so if anyone has a suggestion, I am open. We move the platform specific member of the mutex into its own platform specific class that the main Mutex class inherits from. Functions are implemented in their respective platform specific compilation units. For Fuchsia, we use the sync APIs, as those are also the ones being used in Scudo. Differential Revision: https://reviews.llvm.org/D90351 | 5 年前 | |
[GWP-ASan] Fuchsia specific mapping & utilities functions This CL introduces the Fuchsia versions of the existing platform specific functions. For Fuchsia, we need to track the VMAR (https://fuchsia.dev/fuchsia-src/reference/kernel_objects/vm_address_region) of the Guarded Pool mapping, and for this purpose I added some platform specific data structure that remains empty on POSIX platforms. getThreadID is not super useful for Fuchsia so it's just left as a stub for now. While testing the changes in my Fuchsia tree, I realized that guarded_pool_allocator_tls.h should have closed the namespace before including GWP_ASAN_PLATFORM_TLS_HEADER, otherwise drama ensues. This was tested in g3, upstream LLVM, and Fuchsia (with local changes). Differential Revision: https://reviews.llvm.org/D90483 | 5 年前 | |
[GWP-ASan] Change sys/cdefs.h to features.h sys/cdefs.h is a glibc internal header which is not supposed to be included by applications. (Some libc implementations provide this file for compatibility.) Android features.h includes sys/cdefs.h, so we can include features.h instead. This change makes ninja gwp_asan build on musl. | 5 年前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 5 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 3 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 6 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 5 年前 |