diff options
author | Yo Chiang <yochiang@google.com> | 2020-10-21 22:25:21 +0800 |
---|---|---|
committer | Yo Chiang <yochiang@google.com> | 2020-10-26 19:22:58 +0800 |
commit | 0267bf0e963ecedd01b9fe604a84fca1385dc456 (patch) | |
tree | 0166f9f5bef4eb0c54c68e32d8ce883d357a2b6d /trusty/coverage/coverage_test.cpp | |
parent | 346e6792b45cafc8d3b8dcf993584b98743a4688 (diff) |
Enable overlayFS on DSU system
Enable overlayFS (adb remount) within DSU only if the DM device
scratch_gsi exists. Under DSU mode the backing scratch device of
overlayFS must be scratch_gsi. The scratch_gsi partition must be
created by gsid on the host system and initialized during
first-stage-init. fs_mgr_overlayfs mustn't create any scratch device
for DSU, instead it should just check the existence of the dm node
and initialize the scratch partition (if any).
Bug: 165925766
Test: (In host)
adb shell gsi_tool create-partition --partition system \
--size $(du -b system.img | cut -f1) <system.img
adb shell gsi_tool create-partition --readwirte --partition userdata \
--size $((8 * 1024 * 1024 * 1024))
adb shell gsi_tool create-partition --readwirte --partition scratch \
--size $((200 * 1024 * 1024))
adb reboot
Test: (In DSU guest)
# Ensure next reboot is still DSU
adb shell gsi_tool enable
adb remount -R
# Check the output of "adb shell mount"; "/system", "/vendor" ...
# should be remounted as RW.
Test: adb-remount-test.sh in DSU system
Test: adb-remount-test.sh in normal system
Change-Id: I3267f551313e6b4d4ee63a4f1021040076126e6b
Diffstat (limited to 'trusty/coverage/coverage_test.cpp')
0 files changed, 0 insertions, 0 deletions