From 26718da1713a5698070e702e68db1f995baeae07 Mon Sep 17 00:00:00 2001 From: Dave Watson Date: Wed, 17 Jan 2018 08:04:05 -0800 Subject: [PATCH] Use syscall directly in write_validate to avoid ASAN errors ASAN will complain about this write call with the following error: ERROR: AddressSanitizer: stack-buffer-underflow on address HINT: this may be a false positive if your program uses some custom stack unwind mechanism or swapcontext This is similar to what google's abseil does to work around the issue. Reported-by: qiwang@fb.com --- src/x86_64/Ginit.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/src/x86_64/Ginit.c b/src/x86_64/Ginit.c index 6281b767..2a84a1ee 100644 --- a/src/x86_64/Ginit.c +++ b/src/x86_64/Ginit.c @@ -34,6 +34,7 @@ WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. */ #include #include #include +#include #include "unwind_i.h" @@ -107,7 +108,8 @@ write_validate (void *addr) do { - ret = write (mem_validate_pipe[1], addr, 1); + /* use syscall insteadof write() so that ASAN does not complain */ + ret = syscall (SYS_write, mem_validate_pipe[1], addr, 1); } while ( errno == EINTR );