summaryrefslogtreecommitdiff
path: root/libutils/ProcessCallStack.cpp
diff options
context:
space:
mode:
authorSandeep Patil <sspatil@google.com>2017-02-16 18:13:38 -0800
committerSandeep Patil <sspatil@google.com>2017-02-22 11:30:35 -0800
commite9da79bd4466d5bf0d445b90915a9f18942fc7fe (patch)
treed18d6ebeb3119857cedd534cafce5e3783281b54 /libutils/ProcessCallStack.cpp
parent05ff38ba43eb7a882873312f12fc019b42f37b34 (diff)
init: early_mount: create device node for verity metadata partition
Most devices pass the veritymode through 'androidboot.veritymode' kernel cmdline partition. However, for those who don't, the verity state is read from a different block device whose path it passed to "verify=" fs_mgr option in fstab. This change add support for such a case if the partition that needs to be mounted early requires this additional block device to load the verity state from. Note that, there can only be 1 partition to get the verity state regardless of the number of partitions we enable verity for. Bug: 27805372 Test: Test angler by removing the metdata argument in fstab when it boots fine. Tested by adding the argument when it fails to boot as veritymode gets set to EIO during early mount due to lack of access to properties as expected. TODO: fs_mgr must pull the veritymode from kernel cmdline or device tree by itself Change-Id: I9e62b8c1bf2c0ae0365677df697a0cbe9e5810c1 Signed-off-by: Sandeep Patil <sspatil@google.com>
Diffstat (limited to 'libutils/ProcessCallStack.cpp')
0 files changed, 0 insertions, 0 deletions