From de162521ed91e176bc94483163e7ab16a58d47a6 Mon Sep 17 00:00:00 2001 From: Mandeep Singh Baines Date: Thu, 7 Apr 2011 10:12:08 -0700 Subject: [PATCH] build_image: hard-code verity_depth to 0 Plan is to eventually deprecate depth as a configurable parameter. depth=0 means compute the depth based on a regular trie with a single block of hashes at the root node. BUG=chromium-os:9752 TEST=platform_DMVerity Change-Id: I5c5f1b1f2c2079d7e1ef6c7a55c859b463a59aee R=wad@chromium.org,taysom@chromium.org,ups@chromium.org,gauravsh@chromium.org,jimherbert@chromium.org Review URL: http://codereview.chromium.org/6810006 --- build_image | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/build_image b/build_image index ba9ac91809..ed5b8fefaf 100755 --- a/build_image +++ b/build_image @@ -99,8 +99,6 @@ DEFINE_boolean enable_rootfs_verification ${FLAGS_TRUE} \ DEFINE_integer verity_error_behavior 3 \ "Kernel verified boot error behavior (0: I/O errors, 1: panic, 2: nothing, \ 3: cros) Default: 3" -DEFINE_integer verity_depth 3 \ - "Kernel verified boot hash tree depth. Default: 3" DEFINE_integer verity_max_ios -1 \ "Number of outstanding I/O operations dm-verity caps at. Default: -1" DEFINE_string verity_algorithm "sha1" \ @@ -389,7 +387,7 @@ create_boot_desc() { --statefulfs_mountpoint="${STATEFUL_FS_DIR}" --espfs_mountpoint="${ESP_FS_DIR}" --verity_error_behavior="${FLAGS_verity_error_behavior}" - --verity_depth="${FLAGS_verity_depth}" + --verity_depth="0" --verity_max_ios="${FLAGS_verity_max_ios}" --verity_algorithm="${FLAGS_verity_algorithm}" --keys_dir="${DEVKEYSDIR}"