We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
1 parent 53a45b4 commit a3bf742Copy full SHA for a3bf742
README.md
@@ -763,7 +763,7 @@ since they would be useful for:
763
When memory tagging is enabled, checking for write-after-free at allocation
764
time and checking canaries are both disabled. Canaries will be more thoroughly
765
disabled when using memory tagging in the future, but Android currently has
766
-[very dynamic memory tagging support](https://source.android.com/docs/security/test/memory-safety/arm-mte)
+[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.
769
0 commit comments