[roll] Roll fuchsia [kernel][vm] Re-order reference creation

Change the order of code in VMO reference creation so that fallible
checks are performed before constructing the VmObjectPaged. This is
necessary as destructing a partially constructed VmObjectPaged is
unsafe.

Comments and checks in ~VmObjectPaged are updated to reflect this, as
the existing check no longer makes sense as cow_pages_ is const and
assigned at construction.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1206864
Original-Revision: 22a2ab8b794b7d53d7c08829d546c43996026c0d
GitOrigin-RevId: 4c8f662dc279845d354df5a0f8f8e9ce398e6cbf
Change-Id: I8ac09e629da9f865569d0a7e0cdcc6ba970aac05
1 file changed
tree: 4914486959e7c7be083fb93a7282a85a3f3cc702
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. 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 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.