[roll] Roll fuchsia [dm-verity] Use hash_start_block to read leaf nodes from the hash device

Currently, the device mapper reads the leaf nodes of the merkle tree off
the end of the hash device. However, Android might add trailing metadata
to the end of the hash device. Instead, the device mapper should use
hash_start_block and then calculate the size of the merkle tree to
figure out which offset to read the leaf nodes from.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1046613
Original-Revision: 916dfae31bbfe53ff49a3834809bdead06b1f475
GitOrigin-RevId: b9fef2a88265c02fb208adde3d0a105603f17e90
Change-Id: I02cbca4fef548c0ea22f351a9f77031a85ea5062
1 file changed
tree: acbcae61d7076cd41904d909d4e1af1d489c9205
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.