| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
[NFC][Py Reformat] Reformat python files in the rest of the dirs This is an ongoing series of commits that are reformatting our Python code. This catches the last of the python files to reformat. Since they where so few I bunched them together. Reformatting is done with black. If you end up having problems merging this commit because you have made changes to a python file, the best way to handle that is to run git checkout --ours <yourfile> and then reformat it with black. If you run into any problems, post to discourse about it and we will try to help. RFC Thread below: https://discourse.llvm.org/t/rfc-document-and-standardize-python-code-style Reviewed By: jhenderson, #libc, Mordante, sivachandra Differential Revision: https://reviews.llvm.org/D150784 | 3 年前 | |
Revert "sanitizers: increase .clang-format columns to 100" This reverts commit 5d1df6d220f1d6f726d9643848679d781750db64. There is a strong objection to this change: https://reviews.llvm.org/D106436#2905618 Reviewed By: dblaikie Differential Revision: https://reviews.llvm.org/D106847 | 4 年前 | |
[DFSan] Replace cat with cmake -E cat (#90557) CMake supports [this command](https://cmake.org/cmake/help/latest/manual/cmake.1.html#cmdoption-cmake-E-arg-cat) as of version 3.18. [D151344](https://reviews.llvm.org/D151344) bumped the minimum version to 3.20, so, it is now possible to remove the dependency on the external utility. This helps to cross-compile from Windows to Linux without installing additional tools, such as MSYS2. | 2 年前 | |
Reapply "[NFC] Fix CodeQL violations in compiler-rt. (#157793)" (#157913) (#159097) Fix below buildbot failure. /var/lib/buildbot/fuchsia-x86_64-linux/llvm-project/compiler-rt/lib/fuzzer/FuzzerDriver.cpp:172:42: error: use of undeclared identifier 'uint' 172 | Printf("Flag: %s %u\n", Name, (uint)Val); Replace uint with uint32_t cast. This reverts commit 8062b166762b51f1c3a9168e7031babde3e330a8. | 10 个月前 | |
[DFSan] Remove trampolines to unblock opaque pointers. (Reland with fix) https://github.com/llvm/llvm-project/issues/54172 Reviewed By: pcc Differential Revision: https://reviews.llvm.org/D121250 | 4 年前 | |
[dfsan] Propagate origins for callsites This is a part of https://reviews.llvm.org/D95835. Each customized function has two wrappers. The first one dfsw is for the normal shadow propagation. The second one dfso is used when origin tracking is on. It calls the first one, and does additional origin propagation. Which one to use can be decided at instrumentation time. This is to ensure minimal additional overhead when origin tracking is off. Reviewed-by: morehouse Differential Revision: https://reviews.llvm.org/D97483 | 5 年前 | |
[dfsan] Use namespace qualifier and internalize accidentally exported functions. NFC | 1 年前 | |
[sanitizer] Replace ALIGNED with alignas C++11 alignas is already used extensively. alignas must precede static, so adjust the ordering accordingly. msan.cpp: Clang 15 doesn't allow __attribute__((visibility("default"))) alignas(16). Use the order alignas(16) SANITIZER_INTERFACE_ATTRIBUTE. Tested with Clang 7. Pull Request: https://github.com/llvm/llvm-project/pull/98958 | 2 年前 | |
[dfsan] Use namespace qualifier and internalize accidentally exported functions. NFC | 1 年前 | |
[NFC][sanitizer] Rename Lock{Before,After}Fork suffixes locking StackDepotBase (#76279) This is preparation for performance optimization. We need to highlight that this is very specific lock, and should not be used for other purposes. Add fork_child parameter to distinguish processes after fork. | 2 年前 | |
[sanitizer] VReport BeforeFork/AfterFork (#111900) Forks are common suspects for unusual sanitizer behavior. It can be handy to see them without rebuild. | 1 年前 | |
[dfsan] Add origin chain utils This is a part of https://reviews.llvm.org/D95835. The design is based on MSan origin chains. An 4-byte origin is a hash of an origin chain. An origin chain is a pair of a stack hash id and a hash to its previous origin chain. 0 means no previous origin chains exist. We limit the length of a chain to be 16. With origin_history_size = 0, the limit is removed. The change does not have any test cases yet. The following change will be adding test cases when the APIs are used. Reviewed-by: morehouse Differential Revision: https://reviews.llvm.org/D96160 | 5 年前 | |
[dfsan] Make warn_unimplemented off by default Because almost all internal use cases need to turn warn_unimplemented off. | 4 年前 | |
[sanitizer] Remove DTLS_on_libc_memalign (#108120) DTLS_on_libc_memalign is called from primary allocator, so __sanitizer_get_allocated_begin should also be aware of allocation, and correctly handled by GetDTLSRange. | 1 年前 | |
[DFSan] [compiler-rt] leave BufferedStackTrace uninit Otherwise we have to memset 2040 bytes (255 * 8) for each call Pull Request: https://github.com/llvm/llvm-project/pull/102252 | 1 年前 | |
[dfsan] Add origin chain utils This is a part of https://reviews.llvm.org/D95835. The design is based on MSan origin chains. An 4-byte origin is a hash of an origin chain. An origin chain is a pair of a stack hash id and a hash to its previous origin chain. 0 means no previous origin chains exist. We limit the length of a chain to be 16. With origin_history_size = 0, the limit is removed. The change does not have any test cases yet. The following change will be adding test cases when the APIs are used. Reviewed-by: morehouse Differential Revision: https://reviews.llvm.org/D96160 | 5 年前 | |
[dfsan] Re-exec with no ASLR if memory layout is incompatible on Linux (#85674) DFSan's shadow mappings are incompatible with 32 bits of ASLR entropy ('sudo sysctl vm.mmap_rnd_bits=32; ninja check-dfsan') and it is difficult to fix this via increasing the size of the shadow mappings, due to the overhead of shadow memory. This patch works around the issue by detecting if the memory layout is incompatible, and if so, re-exec'ing without ASLR. DFSan and MSan share copy-pasted shadow memory code, hence this workaround is ported from MSan: - "[msan] Re-exec with no ASLR if memory layout is incompatible on Linux" (https://github.com/llvm/llvm-project/commit/58f7251820b14c93168726a24816d8a094599be5) - "[msan] Add 'MappingDesc::ALLOCATOR' type and check it is available" (https://github.com/llvm/llvm-project/commit/af2bf86a372cacf5f536bae06e2f2d3886eefb7b) (which in turn are inspired by TSan: "Re-exec TSan with no ASLR if memory layout is incompatible on Linux" (https://github.com/llvm/llvm-project/commit/0784b1eefa36d4acbb0dacd2d18796e26313b6c5 )) aeubanks had remarked in https://github.com/llvm/llvm-project/pull/85142#issuecomment-2004442883 that this issue occurs in Chromium: https://ci.chromium.org/ui/p/chromium/builders/try/linux_upload_clang/5066/overview | 2 年前 | |
| 1 年前 | ||
[DFSan] Remove trampolines to unblock opaque pointers. (Reland with fix) https://github.com/llvm/llvm-project/issues/54172 Reviewed By: pcc Differential Revision: https://reviews.llvm.org/D121250 | 4 年前 | |
[dfsan] Wrap glibc 2.38 __isoc23_* functions (#79958) Fix #79283: test/dfsan/custom.cpp has undefined symbol linker errors on glibc 2.38 due to lack of wrappers for __isoc23_strtol and __isoc23_scanf family functions. Implement these wrappers as aliases to existing wrappers, similar to https://reviews.llvm.org/D158943 for other sanitizers. strtol in a user program, whether or not _ISOC2X_SOURCE is defined, uses the C23 semantics (strtol("0b1", 0, 0) => 1), when libclang_rt.dfsan.a is built on glibc 2.38+. | 2 年前 | |
[dfsan] Wrap glibc 2.38 __isoc23_* functions (#79958) Fix #79283: test/dfsan/custom.cpp has undefined symbol linker errors on glibc 2.38 due to lack of wrappers for __isoc23_strtol and __isoc23_scanf family functions. Implement these wrappers as aliases to existing wrappers, similar to https://reviews.llvm.org/D158943 for other sanitizers. strtol in a user program, whether or not _ISOC2X_SOURCE is defined, uses the C23 semantics (strtol("0b1", 0, 0) => 1), when libclang_rt.dfsan.a is built on glibc 2.38+. | 2 年前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 3 年前 | ||
| 4 年前 | ||
| 2 年前 | ||
| 10 个月前 | ||
| 4 年前 | ||
| 5 年前 | ||
| 1 年前 | ||
| 2 年前 | ||
| 1 年前 | ||
| 2 年前 | ||
| 1 年前 | ||
| 5 年前 | ||
| 4 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 5 年前 | ||
| 2 年前 | ||
| 1 年前 | ||
| 4 年前 | ||
| 2 年前 | ||
| 2 年前 |