commit 06954185b69745b5b8069049a2fc733f2888fa41
author Rasha Eqbal <rashaeqbal@google.com> Thu Dec 22 23:56:58 2022 +0000
committer CQ Bot <fuchsia-internal-scoped@luci-project-accounts.iam.gserviceaccount.com> Thu Dec 22 23:56:58 2022 +0000
tree d4df983253f273ac41770a7d3532881cfe9e128f
parent 3a1c78447de0370b06e2627f05aea4263334ba5d

[kernel][vm] Introduce ZX_RIGHT_RESIZE

ZX_RIGHT_RESIZE gets added to the new handle if a VMO is created with
the ZX_VMO_RESIZABLE option, or if a child VMO is created with the
ZX_VMO_CHILD_RESIZABLE option.

vmo_set_size validates the ZX_RIGHT_RESIZE right along with the existing
ZX_RIGHT_WRITE check. We might decouple the two and only check for
ZX_RIGHT_RESIZE in the future, but checking for both does not break
current users who control resize with ZX_RIGHT_WRITE.

Test: core-vmo
Bug: 81316
Run-All-Tests: true
Change-Id: I28188600c7adac9d9513af86c02e74d945b0bde7
Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/772403
Size-Review: Gopi Krishna Chitluri <gopichitluri@google.com>
Reviewed-by: Roland McGrath <mcgrathr@google.com>
Reviewed-by: Carlos Pizano Uribe <cpu@google.com>
API-Review: Carlos Pizano Uribe <cpu@google.com>
Commit-Queue: Rasha Eqbal <rashaeqbal@google.com>
Reviewed-by: Adrian Danis <adanis@google.com>
API-Review: Roland McGrath <mcgrathr@google.com>