45f0a3b642
A future version of HWASAN will set pointer tags when taking the address of a global. This means that we need to untag pointers in a couple of cases where potential global pointers are passed to an interface that expects untagged pointers: - The WriteProtected class, whose only instances are globals, passes its own address to mprotect. However, our device kernels do not currently untag pointers passed to mprotect (the proposed upstream kernel patches do, however, untag these pointers), so once HWASAN starts tagging global pointers, this will start failing. - The shadow_load function loads from a shadow that corresponds to the address space bounds of loaded binaries. Since these address space bounds are untagged, the pointer needs to be untagged to match. Test: boots Change-Id: I3f11ce6eb7261752e5ff6d039d04dd45516b236f |
||
|---|---|---|
| .. | ||
| Android.bp | ||
| libdl.cpp | ||
| libdl.map.txt | ||
| libdl_android.cpp | ||
| libdl_android.map.txt | ||
| libdl_cfi.cpp | ||
| libdl_static.cpp | ||
| MODULE_LICENSE_APACHE2 | ||
| NOTICE | ||