[roll] Roll fuchsia [fsverity] Update fsverity state via will_update_mutation

Add a Pending state to both the fsverity_descriptor and the merkle tree
and place both fields under the same mutex, to avoid lock ordering
requirements.

Original-Bug: b/308898343
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/971592
Original-Revision: e6950a5bbb96ff082e50c1707c652b034f16fd9e
GitOrigin-RevId: c8e63b525f3363f492b0e7009377e10b0dc78976
Change-Id: Id273e11b0d8ac7334c73736c519fcec560348c76
1 file changed
tree: 620b142547d3dcadffc0a619b0f59bc7e06c8371
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
  14. 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.