diff options
| author | Tom Cherry <tomcherry@google.com> | 2019-01-07 14:25:31 -0800 |
|---|---|---|
| committer | Tom Cherry <tomcherry@google.com> | 2019-02-11 12:50:22 -0800 |
| commit | cf80b6d6e59a71a80ffc9d7489523137301974cd (patch) | |
| tree | 209c19167ff87ea6643a4ef405078b46bdc985f1 /libunwindstack/tests/MemoryFileTest.cpp | |
| parent | 6576e139958992a75174b09bbb0cec23d3ffb680 (diff) | |
Refactor fs_mgr_update_verity_state()
fs_mgr_update_verity_state() has two callers with generally different
intentions. One caller loops through all entries in the default fstab
to set partition.<mount_point>.verified properties. The other caller
is only interested in whether or a specific mount point has verity
enabled.
Given this, we refactor fs_mgr_update_verity_state() to
fs_mgr_get_verity_mount_point() which takes a single FstabEntry and
returns the mount point used for the dm-verity device or an empty
option if verity is not enabled on that mount point.
Test: adb-remount-test.sh test on blueline
Change-Id: Ic7dd8390509e95b2931b21e544c919a544138864
Diffstat (limited to 'libunwindstack/tests/MemoryFileTest.cpp')
0 files changed, 0 insertions, 0 deletions