[roll] Roll fuchsia [kernel][vm] Clarify zx_vmar_protect docs

The code ensures that all protection changes across mappings in the
range are either atomically applied on success, or not applied at all
for failures other than ZX_ERR_NO_MEMORY. Document this behavior in
syscall docs and code comments.

Original-Bug: 124205
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/824502
Original-Revision: 0192272ed4466409f9584119631b6933e235ab39
GitOrigin-RevId: 8abfa2f785a5e99f99a4253d45f5c6f12c5689e4
Change-Id: I3edab64d8ce67e8d143246a39e531f3ea95a870d
1 file changed
tree: a030f91d87375b6073615d289e9c90ce23f70b67
  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.