[roll] Roll fuchsia [kernel][vm] Do not trim range in OP_DECOMMIT

ZX_VMO_OP_DECOMMIT should fail with ZX_ERR_OUT_OF_RANGE if the range
specified falls outside of the VMO size, as documented in vmo_op_range
syscall docs. Previously the range was silently trimmed.

Original-Bug: 130470
Test: core-vmo
Run-All-Tests: true
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/883141
Original-Revision: 3e12ed24048833586187b3f70ab331375c018d2f
GitOrigin-RevId: 268df305ef036668544729d71bfa3d9e6898ca96
Change-Id: I04113de328bb2b071bf7551e6805407d37a07983
1 file changed
tree: 6a5adc266942a5e1f98031413cf660edc648e401
  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.