jmb/hardened_malloc
1
0
Fork 0
mirror of https://github.com/GrapheneOS/hardened_malloc.git synced 2025-04-19 22:10:19 +02:00
Code Issues Projects Releases Packages Wiki Activity

amend memory tagging README section

Browse source 
Memory tagging is enabled by default in bionic, but can be disabled at any point.
Memory tagging can't be re-enabled after it's disabled.
This commit is contained in:
Dmitry Muhomor 2024-01-23 19:11:12 +02:00
parent 053c71e8e2
commit 89a7bc631f
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
README.md
View file

@ -764,8 +764,8 @@ When memory tagging is enabled, checking for write-after-free at allocation
time and checking canaries are both disabled. Canaries will be more thoroughly
disabled when using memory tagging in the future, but Android currently has
[very dynamic memory tagging support](https://source.android.com/docs/security/test/memory-safety/arm-mte)
where it can be enabled/disabled at any time which creates a barrier to
optimizing by disabling redundant features.
where it can be disabled at any time which creates a barrier to optimizing
by disabling redundant features.
## API extensions