diff options
| author | Nikita Ioffe <ioffe@google.com> | 2019-12-19 21:18:42 +0000 |
|---|---|---|
| committer | Nikita Ioffe <ioffe@google.com> | 2019-12-19 21:18:42 +0000 |
| commit | 3d6a5fcb87e495ea6b0c552b82b537cd0981f652 (patch) | |
| tree | 5f60d582c9b7e0948c71f43dbcfa7398fb96b1c7 /libutils/ProcessCallStack_fuzz.cpp | |
| parent | a1344fa6d7622a4dd44e2eb91bc3455f3363d99d (diff) | |
Now for real unmount bind-mounts on top of /data
Approach in
https://android-review.googlesource.com/c/platform/system/core/+/1191457
depended on ordering of entries. Instead fs_mgr now tries to unmount
everything with the same block device as /data until timeout is reached.
This is very similar to what is done in UmountPartitions in reboot.cpp,
but I'm a little bit reluctant to merge them together, since the later
unmount all read-write partitions, while here we are only interested in
/data.
Test: on both coral and blueline:
Test: adb shell /system/bin/vdc checkpoint startCheckpoint 1
Test: adb shell setprop sys.init.userdata_remount.force_umount_f2fs 1
Test: adb reboot userspace
Test: verified that userdata was remounted
Bug: 135984674
Change-Id: I929a058fa2f9639f0a2b73e9ea269cf1e07db889
Diffstat (limited to 'libutils/ProcessCallStack_fuzz.cpp')
0 files changed, 0 insertions, 0 deletions