[roll] Roll fuchsia [kernel][vm] Validate stream size for ZX_VMO_UNBOUNDED

Adds a validation check in zx_vmo_create to ensure that the
user-supplied initial stream size does not exceed VmObject::MAX_SIZE.

This handles cases where ZX_VMO_UNBOUNDED is passed, which sets the VMO
backing size to MAX_SIZE, preventing callers from initializing a data
stream size larger than the maximum VMO capacity.

Original-Bug: 506441830
Test: core-tests (core-vmo: CreateVmoUnboundedInvalidStreamSize)
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1597277
Original-Revision: c1913920298c655c877749dc6a9bb75686b7b518
GitOrigin-RevId: de5fbb31dab5f123d899c5f1d3af0a4793a124ac
Change-Id: I62b3ab0a6d0fea3e228efb9261d36e1c6f97f5a7
1 file changed
tree: af580ed127820f49e7316d0ad8a29c7b382d9501
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cobalt
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
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.