[Asan] Fix false leak report

If user thread is in the allocator, the allocator
may have no pointer into future user's part of
the allocated block. AddrIsInside ignores such
pointers and lsan reports a false memory leak.

Reviewed By: morehouse

Differential Revision: https://reviews.llvm.org/D87552

compiler-rt/lib/asan/asan_allocator.cpp

@@ -1117,13 +1117,11 @@ uptr PointsIntoChunk(void* p) {
   if (!m || atomic_load(&m->chunk_state, memory_order_acquire) !=
                 __asan::CHUNK_ALLOCATED)
     return 0;
-  uptr chunk = m->Beg();
+  // AsanChunk presence means that we point into some block from underlying
-  if (m->AddrIsInside(addr, /*locked_version=*/true))
+  // allocators. Don't check whether p points into user memory, since until
-    return chunk;
+  // the return from AsanAllocator::Allocator we may have no such
-  if (IsSpecialCaseOfOperatorNew0(chunk, m->UsedSize(/*locked_version*/ true),
+  // pointer anywhere. But we must already have a pointer to GetBlockBegin().
-                                  addr))
+  return m->Beg();
-    return chunk;
-  return 0;
 }
 
 uptr GetUserBegin(uptr chunk) {

compiler-rt/test/asan/TestCases/redzone_noleak.cpp

@@ -0,0 +1,28 @@
+// Test whether pointers into left redzone count memory are reachable.
+// If user thread is inside asan allocator code then we may have no
+// pointers into user part of memory yet. However we should have a pointer
+// into the allocated memory chunk.
+//
+// RUN: %clangxx_asan  %s -o %t
+// RUN: %run %t 2>&1
+
+#include <cstdlib>
+#include <stdio.h>
+#include <thread>
+
+void *pointers[1000];
+void **cur = pointers;
+
+void leak(int n, int offset) {
+  printf("%d %d\n", n, offset);
+  for (int i = 0; i < 3; ++i)
+    *(cur++) = (new int[n]) + offset;
+}
+
+int main(int argc, char **argv) {
+  for (int n = 1; n < 10000000; n = n * 2) {
+    leak(n, 0);
+    leak(n, -1);
+  }
+  return 0;
+}