summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMary Ruthven <mruthven@chromium.org>2021-02-24 16:09:47 +0000
committerCommit Bot <commit-bot@chromium.org>2021-02-24 16:25:24 +0000
commit3ee029033e57c6ee20a917c3237ffad3fd85a734 (patch)
tree999e5388847615b9de916ee530d841fe054a458b
parent223a2a14adbbe1095b3f12434925ff5f704eac73 (diff)
downloadchrome-ec-3ee029033e57c6ee20a917c3237ffad3fd85a734.tar.gz
Revert "ap_ro_hash: add a maximum number of ranges"
This reverts commit d7e4695a3e454303be034825292dca49cdebe630. Reason for revert: Revert to reland in correct order. Original change's description: > ap_ro_hash: add a maximum number of ranges > > It's unlikely any factory process will try to use more than 32 ranges. > This change adds a hard limit to ensure they don't. > > BUG=none > TEST=none > > Change-Id: I411777c15e52c0af7a59e717bdacbae092dad3ab > Signed-off-by: Mary Ruthven <mruthven@chromium.org> > Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2547196 > Reviewed-by: Vadim Bendebury <vbendeb@chromium.org> > (cherry picked from commit 26b886623c4e2184f142498b769c415b4e08ac38) > Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2669285 > (cherry picked from commit b807edf02c14ed175dd2ec90c131347ff00b4e7d) > Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2713834 Bug: none Change-Id: I9fc0692586bf3477314942482d0abcd7fe1ab764 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2718409 Auto-Submit: Mary Ruthven <mruthven@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Commit-Queue: Mary Ruthven <mruthven@chromium.org>
-rw-r--r--common/ap_ro_integrity_check.c14
-rw-r--r--include/tpm_vendor_cmds.h1
2 files changed, 0 insertions, 15 deletions
diff --git a/common/ap_ro_integrity_check.c b/common/ap_ro_integrity_check.c
index ec11e54fd2..bb9f62abd6 100644
--- a/common/ap_ro_integrity_check.c
+++ b/common/ap_ro_integrity_check.c
@@ -27,16 +27,6 @@ struct flash_range {
uint32_t range_size;
} __packed;
-/*
- * A somewhat arbitrary maximum number of AP RO hash ranges to save. There are
- * 27 regions in a FMAP layout. The AP RO ranges should only be from the RO
- * region. It's unlikely anyone will need more than 32 ranges.
- * If there are AP RO hash issues, the team will likely need to look at the
- * value of each range what part of the FMAP it corresponds to. Enforce a limit
- * to the number of ranges, so it's easier to debug and to make people consider
- * why they would need more than 32 ranges.
- */
-#define APRO_MAX_NUM_RANGES 32
/* Values used for sanity check of the flash_range structure fields. */
#define MAX_SUPPORTED_FLASH_SIZE (32 * 1024 * 1024)
#define MAX_SUPPORTED_RANGE_SIZE (4 * 1024 * 1024)
@@ -142,10 +132,6 @@ static enum vendor_cmd_rc vc_seed_ap_ro_check(enum vendor_cmd_cc code,
vc_num_of_ranges =
(input_size - SHA256_DIGEST_SIZE) / sizeof(struct flash_range);
- if (vc_num_of_ranges > APRO_MAX_NUM_RANGES) {
- *response = ARCVE_TOO_MANY_RANGES;
- return VENDOR_RC_BOGUS_ARGS;
- }
for (i = 0; i < vc_num_of_ranges; i++) {
if (vc_payload->ranges[i].range_size >
MAX_SUPPORTED_RANGE_SIZE) {
diff --git a/include/tpm_vendor_cmds.h b/include/tpm_vendor_cmds.h
index 179f8e8e06..20336f637d 100644
--- a/include/tpm_vendor_cmds.h
+++ b/include/tpm_vendor_cmds.h
@@ -253,7 +253,6 @@ enum ap_ro_check_vc_errors {
ARCVE_FLASH_WRITE_FAILED = 6,
ARCVE_BID_PROGRAMMED = 7,
ARCVE_FLASH_ERASE_FAILED = 8,
- ARCVE_TOO_MANY_RANGES = 9,
};
/* Structure for VENDOR_CC_SPI_HASH request which follows tpm_header */