Skip to content

Commit 3c1f40a

Browse files
muhomorrthestinger
authored andcommitted
amend memory tagging README section
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.
1 parent 5fbbdc2 commit 3c1f40a

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -764,8 +764,8 @@ When memory tagging is enabled, checking for write-after-free at allocation
764764
time and checking canaries are both disabled. Canaries will be more thoroughly
765765
disabled when using memory tagging in the future, but Android currently has
766766
[very dynamic memory tagging support](https://source.android.com/docs/security/test/memory-safety/arm-mte)
767-
where it can be enabled/disabled at any time which creates a barrier to
768-
optimizing by disabling redundant features.
767+
where it can be disabled at any time which creates a barrier to optimizing
768+
by disabling redundant features.
769769

770770
## API extensions
771771

0 commit comments

Comments
 (0)