Sami Tolvanen 2f42554f18 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 Change-Id: Iaf28185adb8b80e5452447e54e1f4e4417a34168		2015-07-15 09:11:13 +00:00
..
include	Merge "Set verity mode as the verified property value"	2015-04-07 08:45:24 +00:00
Android.mk	Revert "Revert "fs_mgr_verity: Add support for squashfs""	2015-04-08 18:08:00 -07:00
fs_mgr.c	Only pass nomblk_io_submit option when mounting ext4	2015-06-09 16:38:35 +00:00
fs_mgr_fstab.c	Revert "Revert "Adding e4crypt support""	2015-03-31 13:02:13 -07:00
fs_mgr_main.c	Cleanup: warning fixit.	2014-04-11 16:15:46 -07:00
fs_mgr_priv.h	Revert "Revert "Adding e4crypt support""	2015-03-31 13:02:13 -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 09:11:13 +00:00