commit | e77a68f67fe22c13e8cb982c4e8b399974632dff | [log] [tgz] |
---|---|---|
author | Jeremy Compostella <jeremy.compostella@intel.com> | Mon May 23 13:10:23 2016 +0200 |
committer | Jeremy Compostella <jeremy.compostella@intel.com> | Mon May 23 13:10:23 2016 +0200 |
tree | 86276f8fff255a0007334c11e044f59b44fbb899 | |
parent | 14352497f02c38d4f9df46820284c100a1fb58d3 [diff] |
slot_metadata: add verity_corrupted field In rootfs context, the verity mode must be supplied by the bootloader to the kernel. This patch creates a new verity_corrupted field in the slot metadata structure to remind that this slot is corrupted from a dm-verity point of view. If the bootloader receives the "dm-verity device corrupted" reboot target, it should set this bit to 1. If this bit value is 1, the bootloader should set the veritymode to "eio". Change-Id: I9335a39d7d009200318c58c53a3139d542788a9b Signed-off-by: Jeremy Compostella <jeremy.compostella@intel.com>
mm -j && m ramdisk-nodeps && m recoveryimage-nodeps # To boot into the new recovery image # without flashing the recovery partition: adb reboot bootloader fastboot boot $ANDROID_PRODUCT_OUT/recovery.img
# After setting up environment and lunch. mmma -j bootable/recovery # Running the tests on device. adb root adb sync data # 32-bit device adb shell /data/nativetest/recovery_unit_test/recovery_unit_test adb shell /data/nativetest/recovery_component_test/recovery_component_test # Or 64-bit device adb shell /data/nativetest64/recovery_unit_test/recovery_unit_test adb shell /data/nativetest64/recovery_component_test/recovery_component_test