cros_make_image_bootable: default to verity_depth=0

Verity only supports a depth of 0. Passing anything other than 0 will
cause a verity failure.

BUG=14314
TEST=Verified that verity does not fail when do depth is passed.
     Before this change, verity would fail with the error message
     reported in the bug.

Change-Id: I68495c4486284744ee0779b6c9cdc0ef214519c7

R=gauravsh@google.com,scottz@google.com,drewry@google.com

Review URL: http://codereview.chromium.org/6873134
This commit is contained in:
Mandeep Singh Baines 2011-04-20 16:28:54 -07:00
parent dc2cb4b8f6
commit 95026958c1

View File

@ -97,7 +97,8 @@ DEFINE_boolean enable_rootfs_verification ${FLAGS_FALSE} \
"Default all bootloaders to use kernel-based root fs integrity checking."
DEFINE_integer verity_error_behavior 2 \
"Kernel verified boot error behavior (0: I/O errors, 1: reboot, 2: nothing)"
DEFINE_integer verity_depth 1 \
# TODO(msb) remove this option (http://crosbug.com/14357)
DEFINE_integer verity_depth 0 \
"Kernel verified boot hash tree depth"
DEFINE_integer verity_max_ios 1024 \
"Number of outstanding I/O operations dm-verity caps at."