Sami Tolvanen
authored
Currently, the device doesn't mount verified partitions if the verity table signature is invalid, which usually means it fails to boot. This change instead sets up dm-verity with an invalid root hash and triggers device-specific error handling to recover from the corruption. Bug: 24256506 Change-Id: I6d693306fa0e7459c5500b028e433df61ecea6fb (cherry picked from commit 47caa5c3)
| Name | Last commit | Last update |
|---|---|---|
| .. | ||
| include | resolved conflicts for merge of d0b6de41 to master | |
| Android.mk | resolved conflicts for merge of 79f33846 to lmp-mr1-dev-plus-aosp | |
| fs_mgr.c | DO NOT MERGE Securely encrypt the master key | |
| fs_mgr_format.c | fs_config: replace getenv('OUT') by new fs_config parameter | |
| 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 | |
| fs_mgr_main.c | Cleanup: warning fixit. | |
| fs_mgr_priv.h | resolved conflicts for merge of d0b6de41 to master | |
| fs_mgr_priv_verity.h | Revert "Revert "Enable verity on userdebug, and add disable-verity to adb"" | |
| fs_mgr_verity.c | fs_mgr: trigger dm-verity error handling for invalid signatures | |