From 3c1f40aff0865dac62b4d5cb36968ff0b97a185c Mon Sep 17 00:00:00 2001 From: Dmitry Muhomor Date: Tue, 23 Jan 2024 19:11:12 +0200 Subject: [PATCH] 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. --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index fe5c5bf..76a4f6d 100644 --- a/README.md +++ b/README.md @@ -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