This reverts commit 4a1f9459e5.
The Chrome issue has been fixed upstread and this workaround is no
longer needed; in fact, it triggers another issue where conflicting MTE
mode settings make newer Chrome versions crash at startup.
Bug: 297266100
Bug: 305005339
Bug: https://crbug.com/1515053
Test: chrome still does not crash; debuggerd shows MTE is enabled (grep
for TCF_MTE)
Change-Id: Iee2b704c4ea39b5809193c1ceed3b8f41618dd40
Cherry-picked from 19eb98145d.
Trigger fsck on mount of /data if the value of ro.preventative_fsck is
not equal to the contents of /metadata/vold/preventative_fsck, then set
the file to the property to prevent future runs
See b/305658663 for context
Bug: 305658663
Test: Make sure fsck run after first boot and not after second
Change-Id: Ie6b9fc94752d91e77e8fc48979216917c1fd9ec3
Signed-off-by: Jaegeuk Kim <jaegeuk@google.com>
Temporarily reset the max page size on zuma devices to 4096 to avoid
extra gap VMAs in P23 devices for qpr1.
Bug: 300942232
Test: readelf -Wl /system/bin/init
Change-Id: I1fda0599a21c633292062db1278df0fed50de23e
Signed-off-by: Kalesh Singh <kaleshsingh@google.com>
This is a no-op in regular builds. Impact is limited to a testing-only
_fullmte build.
Bug: 297266100
Test: chrome does not crash
Change-Id: Iba9b031fa9d2df0c093f0465ae2dd8e1b36133b9
Bug: 280343521
Test: debuggerd `pidof system_server` | head -30 | grep tagged_addr
does not include PR_MTE_
Change-Id: I64e3cf43162c8ab39f45b37240e26c2f25ea964e
This will enable the "Reboot with MTE" developer options button as
described in
https://source.android.com/docs/security/memory-safety/bootloader-support
Bug: 242244112
Test: * all _fullmte products define arm64.memtag.bootctl_supported.
* other products do not define arm64.memtag.bootctl_supported.
* non-fullmte products support "Reboot with MTE" flow as per the
link above.
Change-Id: Ic0e301755fb6745be55b2fb502b530495bef4ca0
