[roll] Roll fuchsia [kernel][vm] Unlocked child range update

Adds a new RangeChangeCowChildren method that consumes the lock,
instead of just operating under it. Long term with fine grained locking
iterating over the children while continuously holding the current lock
will not be possible and this method will have to be used instead.

Introducing this method, and having it just re-direct to the regular
locked version, is intended to allow a gradual transition of call sites
as they will need updating to be tolerant of their lock being dropped.

Original-Bug: 338300943
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1218444
Original-Revision: df0d7bb15d3665e4571b11b12ab697c205fca966
GitOrigin-RevId: 516f47a879c3ba1be2b9f64a95dcb1807d763d0d
Change-Id: If9cd94dad9be65e705e14df1ad6b0cf49bf88530
1 file changed
tree: cbfe1a4e4835d8808e3a8b748a2d4b6bfa05f07a
  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 in one of the communication channels documented at get involved.

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.