StrixOS/build
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Make output of MakeVbmeta consistent

Browse Source 
The order of items in `partitions` map is non-deterministic. To make
sure that builds are hermetic, sort the map before use.

Test: th
Bug: 332550989
Change-Id: I76c7037ef9f03904899339813819fcf985a7c893
This commit is contained in:
Kelvin Zhang
2024-04-15 09:43:07 -07:00
parent a40c6380a1
commit 1d9b3daad2
2 changed files with 2 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
tools/releasetools/add_img_to_target_files.py
View File

@@ -1055,20 +1055,6 @@ def AddImagesToTargetFiles(filename):
for call in add_partition_calls:
add_partition(*call)
else:
# When calling avbtool make_vbmeta_image, it uses the `partitions`
# dictionary to include the options for --include_descriptors_from_image.
# The vbmeta image is different if the order of the
# --include_descriptors_from_image changes. As the images are generated
# parallelly and entries are added on completion of image creation,
# this `partitions` dict might be indeterministic as the order of
# completion of image creation cannot be predicted.
# To address this issue, add keys to the dict `partitions` with null values
# in the order they are listed in the variable `add_partition_calls`, and
# then the values are updated by `add_partition` keeping the order of the
# items. This ensures generated vbmeta.img is the same for the same input.
for call in add_partition_calls:
if call[1]:
partitions[call[0]] = None
with ThreadPoolExecutor(max_workers=len(add_partition_calls)) as executor:
for future in [executor.submit(add_partition, *call) for call in add_partition_calls]:
future.result()