| commit | feeb14f9360e0d4123ae75d52f13977ff74898a8 | [log] [tgz] |
|---|---|---|
| author | Ji-Hwan Lee <jihwan@google.com> | Thu Dec 15 03:53:24 2011 +0900 |
| committer | Ji-Hwan Lee <jihwan@google.com> | Thu Dec 15 04:37:22 2011 +0900 |
| tree | 11296ce58f5deda277851c56c27e23461710d1b2 | |
| parent | a296107eba63341d73b586559fe6dc73439d6f81 [diff] |
Fix invalid madvise() during concurrent alloc/dealloc of MemoryDealer Currently, madvise(MADV_REMOVE) is called after deallocation. Another thread might allocate (and even write) the same region between deallocation and madvise(), in which case the new thread will fail to read what it have written. So, call deallocate() after madvise(MADV_REMOVE). Bug: 5654596 Change-Id: I26f36cd6013de499090768a0ddc68206a4a68219