summaryrefslogtreecommitdiff
path: root/mtectrl
diff options
context:
space:
mode:
authorFlorian Mayer <fmayer@google.com>2023-09-27 15:59:22 -0700
committerFlorian Mayer <fmayer@google.com>2023-09-27 16:03:17 -0700
commit406ed7913d0b6a2586f7eb5f2bcde2cbdaac7551 (patch)
tree85ec92c15d6cb4189ee2a6a1e26d6027e66fe400 /mtectrl
parentca36a936b3c7ba5a2cd00fdcff37cb75a9aa6248 (diff)
downloadextras-406ed7913d0b6a2586f7eb5f2bcde2cbdaac7551.tar.gz
Run mtectrl later in boot sequence
If we run it too early, we fail to run the first time after a factory reset, because /metadata isn't set up properly yet. Test: factory reset and dmesg Bug: 302188718 Change-Id: I35fc8e992d98bd1126bb6c7673d9561b6c9c32e8
Diffstat (limited to 'mtectrl')
-rw-r--r--mtectrl/mtectrl.rc2
1 files changed, 1 insertions, 1 deletions
diff --git a/mtectrl/mtectrl.rc b/mtectrl/mtectrl.rc
index cba3e255..9a85d224 100644
--- a/mtectrl/mtectrl.rc
+++ b/mtectrl/mtectrl.rc
@@ -22,7 +22,7 @@ on property:persist.device_config.runtime_native_boot.bootloader_override=*
# adbd gets initialized in init, so run before that. this makes sure that the
# user does not change the value before we initialize it
-on early-init && property:ro.arm64.memtag.bootctl_supported=1
+on early-boot && property:ro.arm64.memtag.bootctl_supported=1
exec_background -- /system/bin/mtectrl -s arm64.memtag.bootctl -f arm64.memtag.bootctl_loaded
on shutdown && property:ro.arm64.memtag.bootctl_supported=1