Sami Tolvanen 83d8701b06 Update partition.*.verified even with ro.boot.veritymode set ... We need to have partition.*.verified properties even when bootloader is managing dm-verity mode, because we may have failed to set up the verified partition and need a property to indicate this. This means we still need to run fs_mgr_update_verity_state and walk through all the partitions to verify the device mapper status, just without updating verity mode. Bug: 22489805 Bug: 22507568 Change-Id: Iaf28185adb8b80e5452447e54e1f4e4417a34168 (cherry picked from commit 2f42554f18)		2015-07-15 19:13:43 +00:00
..
include	resolved conflicts for merge of d0b6de41 to master	2015-04-13 18:01:33 -07:00
Android.mk	resolved conflicts for merge of 79f33846 to lmp-mr1-dev-plus-aosp	2015-04-13 16:29:05 -07:00
fs_mgr.c	DO NOT MERGE Securely encrypt the master key	2015-05-29 17:39:16 +00:00
fs_mgr_format.c	fs_config: replace getenv('OUT') by new fs_config parameter	2015-07-09 21:47:07 -07:00
fs_mgr_fstab.c	am 2557cd21: am 8b448629: am 16092b7a: Merge "fs_mgr: allow for zramsize to be specified as percentage of total memory" into lmp-mr1-dev	2015-05-13 17:07:53 +00:00
fs_mgr_main.c	Cleanup: warning fixit.	2014-04-11 16:15:46 -07:00
fs_mgr_priv.h	resolved conflicts for merge of d0b6de41 to master	2015-04-13 18:01:33 -07:00
fs_mgr_priv_verity.h	Revert "Revert "Enable verity on userdebug, and add disable-verity to adb""	2014-12-09 17:02:17 -08:00
fs_mgr_verity.c	Update partition.*.verified even with ro.boot.veritymode set	2015-07-15 19:13:43 +00:00