In that case it is very likely that there will be a tag mismatch anyway.
We handle the case that the pointer belongs to neither of the allocators
by getting a nullptr from allocator.GetBlockBegin.
Paths
| Differential D108383
[hwasan] do not check if freed pointer belonged to allocator. ClosedPublic Authored by fmayer on Aug 19 2021, 9:08 AM.
Details Summary In that case it is very likely that there will be a tag mismatch anyway. We handle the case that the pointer belongs to neither of the allocators
Diff Detail
Event TimelineThis revision is now accepted and ready to land.Aug 19 2021, 12:01 PM Closed by commit rG119146f8ae25: [hwasan] do not check if freed pointer belonged to allocator. (authored by fmayer). · Explain WhyAug 20 2021, 2:13 AM This revision was automatically updated to reflect the committed changes. Comment Actions This seems to break tests: http://45.33.8.238/linux/54105/step_10.txt Any idea what's going wrong there? (@pcc too) fmayer added a reverting change: rGde916a7b12ad: Revert "[hwasan] do not check if freed pointer belonged to allocator.".Aug 20 2021, 4:21 AM This revision is now accepted and ready to land.Aug 20 2021, 4:22 AM Closed by commit rG023f18bbaf67: [hwasan] do not check if freed pointer belonged to allocator. (authored by fmayer). · Explain WhyAug 25 2021, 1:31 AM This revision was automatically updated to reflect the committed changes.
Revision Contents
Diff 368105 compiler-rt/lib/hwasan/hwasan_allocator.cpp
compiler-rt/lib/hwasan/hwasan_linux.cpp
compiler-rt/test/hwasan/TestCases/wild-free-realloc.c
compiler-rt/test/hwasan/TestCases/wild-free.c
|