fs_mgr: remove same partition check for vbmeta

With chained vbmeta and especially its use with dynamic partitions,
this check is no longer always true.  A concrete example is the
chained vbmeta_system partition that contains the metadata for /system
and /product_services for mainline devices.

Test: blueline_mainline boots with AVB enabled
Change-Id: Ib4115831bb3bb49bf6d2a908df59ba32f8405de7
This commit is contained in:
Tom Cherry 2018-11-09 10:13:13 -08:00
parent 64ae77e526
commit 1bc8dcd92f
1 changed files with 0 additions and 11 deletions

View File

@ -322,17 +322,6 @@ static bool get_hashtree_descriptor(const std::string& partition_name,
continue;
}
// Ensures that hashtree descriptor is in /vbmeta or /boot or in
// the same partition for verity setup.
std::string vbmeta_partition_name(verify_data.vbmeta_images[i].partition_name);
if (vbmeta_partition_name != "vbmeta" &&
vbmeta_partition_name != "boot" && // for legacy device to append top-level vbmeta
vbmeta_partition_name != partition_name) {
LWARNING << "Skip vbmeta image at " << verify_data.vbmeta_images[i].partition_name
<< " for partition: " << partition_name.c_str();
continue;
}
for (size_t j = 0; j < num_descriptors && !found; j++) {
AvbDescriptor desc;
if (!avb_descriptor_validate_and_byteswap(descriptors[j], &desc)) {