diff options
| author | Bowgo Tsai <bowgotsai@google.com> | 2017-05-11 22:05:23 +0800 |
|---|---|---|
| committer | Bowgo Tsai <bowgotsai@google.com> | 2017-05-13 13:24:12 +0800 |
| commit | 6879cc1e2ee91f47fa05a01dfbce9dfef7504501 (patch) | |
| tree | 114a7b632ae2d5db05587f6cdba5aea227559c89 /trusty/coverage/coverage_test.cpp | |
| parent | 44673da3eb1b2fed013bdc1e2c158e3ef5020456 (diff) | |
fs_mgr: support different dm-verity error modes
AVB is going to support different modes to handle dm-verity errors.
See the following CL for more details:
- https://android-review.googlesource.com/#/c/392873/
The verity mode is controlled by bootloader through androidboot.veritymode in
kernel command line. fs_mgr should read the value from there and specify the
corresponding flag when loading dm-verity table into kernel.
Also removes some unused #include libraries.
Bug: 38157502
Test: Manually tested different dm verity modes:
- "restart_on_corruption" (androidboot.veritymode=enforcing)
- "ignore_corruption" (androidboot.veritymode=logging)
- None, default mode is EIO in kernel (androidboot.veritymode=eio)
Change-Id: I80e1e817a148b54fb67ba58112d376dc2cf37c98
Diffstat (limited to 'trusty/coverage/coverage_test.cpp')
0 files changed, 0 insertions, 0 deletions