[roll] Roll fuchsia [kernel][process] No lock GetAspaceMaps

Avoids holding the ProcessDispatcher lock whilst performing the
GetVmAspaceMaps call. If the process is destroyed the aspace will also
be destroyed and so ZX_ERR_BAD_STATE will still get returned. Not
holding the lock allows for the user copy operations in GetVmAspaceMaps
to not fault with locks held.

Original-Bug: 94078
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/660524
Original-Revision: b5ac534f1419d747e06abfbf73b51d01d0a7c7b1
GitOrigin-RevId: 3b6d7f1f6ad979dc7b090485fcb477b96b56ef59
Change-Id: If4fb065ee08edf7e5ba35f7d137391ca838bf519
1 file changed
tree: 3f3761a699961998f6f2dd46cd272f7e8cb9b374
  1. infra/
  2. third_party/
  3. cts
  4. firmware
  5. flower
  6. jiri.lock
  7. minimal
  8. prebuilts
  9. README.md
  10. stem
  11. test_durations
  12. 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.