On Darwin, simple C null-terminated constant strings normally end up in the __TEXT,__cstring section of the resulting Mach-O binary. When instrumented with ASan, these strings are transformed in a way that they cannot be in __cstring (the linker unifies the content of this section and strips extra NUL bytes, which would break instrumentation), and are put into a generic __const section. This breaks some of the tools that we have: Some tools need to scan all C null-terminated strings in Mach-O binaries, and scanning all the contents of __const has a large performance penalty. This patch instead introduces a special section, __asan_cstring which will now hold the instrumented null-terminated strings.
Details
- Reviewers
kcc filcab dvyukov m.ostapenko eugenis zaks.anna - Commits
- rGbf6e7848a0e2: [asan] Move instrumented null-terminated strings to a special section, compiler…
rGa28c9e8f09c9: [asan] Move instrumented null-terminated strings to a special section, LLVM part
rCRT285620: [asan] Move instrumented null-terminated strings to a special section, compiler…
rL285620: [asan] Move instrumented null-terminated strings to a special section, compiler…
rL285619: [asan] Move instrumented null-terminated strings to a special section, LLVM part
Diff Detail
Event Timeline
lib/Transforms/Instrumentation/AddressSanitizer.cpp | ||
---|---|---|
1539 | Oh, too many nested ifs here. Could you use && instead? |
LGTM
lib/Transforms/Instrumentation/AddressSanitizer.cpp | ||
---|---|---|
1543 | Should this have SectionKind::getReadOnly()? |
lib/Transforms/Instrumentation/AddressSanitizer.cpp | ||
---|---|---|
1543 | Kuba pointed out that this API does not take the Kind. The section will be read-only because it is in the __TEXT segment. |
Is it possible to also add a runnable test to compiler-rt?
I expect to make some changes here soon: https://github.com/google/sanitizers/issues/260#issuecomment-250062528
And by doing that may break your test and your fix.
Updating patch. Lowering the number of nested ifs. Adding a testcase for compiler-rt. Updating the odr-lto.cc testcase.
projects/compiler-rt/test/asan/TestCases/Darwin/odr-lto.cc | ||
---|---|---|
11 | What happened here? There's no error any more? Do we still need to use -asan-use-private-alias, etc? |
ping
projects/compiler-rt/test/asan/TestCases/Darwin/odr-lto.cc | ||
---|---|---|
11 | This tests checks that -asan-use-private-alias fixes a known bug when using LTO+ASan. Eventually, I wanted to turn -asan-use-private-alias on by default to get rid of this annoying bug causing many false positives. This patch fixes accidentally also this bug for a lot of cases (when strings are involved), but I believe there are other (less common) instances of the LTO+ASan bug that aren’t fixed. I would still like to keep the odr-lto.cc testcase, because it tests that -asan-use-private-alias doesn’t regress. If you want me to, I can try to create a new test that would trigger the LTO+ASan bug. |
Updating the ODR testcase. If the global is not a C string (e.g. it contains a NUL byte), it will not be moved to __asan_cstring section, but LTO still likes to merge such globals.
Oh, too many nested ifs here. Could you use && instead?