diff options
| author | Nikita Ioffe <ioffe@google.com> | 2020-03-06 17:36:05 +0000 |
|---|---|---|
| committer | Nikita Ioffe <ioffe@google.com> | 2020-03-11 19:21:37 +0000 |
| commit | 17824f0590785adc77181ad5f937aa5c50ebf2fe (patch) | |
| tree | d5a1ec145d96d9ef75d9dab8eb509b20ab528589 /trusty/coverage/coverage.cpp | |
| parent | f1e27502e4d44291d90b2a397d4991122fcb090b (diff) | |
fs_mgr_get_mounted_entry_for_userdata: handle logical partitions
In case of GSI on DSU, /data is mounted on the following stack:
userdata -> userdata_gsi -> actual block device, and fstab returned from
ReadDefaultFstab() function will say that /data should be
mounted onto userdata_gsi. This configuration wasn't supported.
To support it, fs_mgr_get_mounted_entry_for_userdata now unwinds the
dm-device stack /data is mounted onto, and for each entry in fstab
resolves corresponding block device (in case of logical partitions by
asking DeviceMapper to resolve name -> path, and for other cases by
reading a symlink), and then checking whenever resolved block device
belongs to the unwinded stack.
Test: on both normal boot & DSU
Test: atest CtsUserspaceRebootHostSideTestCases
Test: atest CtsFsMgrTestCases
Bug: 148612148
Change-Id: I1bb3e64ae92d56de905b4f7f1997b7499b101b0f
Merged-In: I1bb3e64ae92d56de905b4f7f1997b7499b101b0f
(cherry picked from commit f495fe798b180345371beec82e4aa74c5feb0dea)
Diffstat (limited to 'trusty/coverage/coverage.cpp')
0 files changed, 0 insertions, 0 deletions