[roll] Roll fuchsia [dm-verity] Implement the device mapper

"The device mapper is a framework for mapping physical block devices
onto higher-level virtual block devices." The device mapper defines
several different kinds of physical devices or targets that it supports.
Android primarily makes use of the "verity" target in order to implement
dm-verity.

Original-Bug: b/338125341
Original-Fixed: b/297432471
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1040296
Original-Revision: c2f159f69728797cf0de7c20d937d792a2e57a2d
GitOrigin-RevId: 1efb314c4b071f4a79b8e38874522c1aad6ec1b4
Change-Id: I457fd166ba9dfcd7c8f869d2acd3f11d73c0577c
1 file changed
tree: deb669c36b684ab6151cbd0c9ca0a4b80db301c2
  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.