[roll] Roll fuchsia [kernel][vm] Restructure clone creation

Restructures the clone creation code to have separate notions of
gaining ownership (via incrementing share counts) of content, and
mechanically hanging the new node either under an existing node or via
hidden parent creation.

Although this split represents a minor performance regression due to
not being able to combine backlink updating and share count
incrementing, it is necessary for the implementation of the parent
content markers.

Original-Bug: 338300943
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1263128
Original-Revision: a0ac49be394c2d00cb46f4df3dca6b5e6688694b
GitOrigin-RevId: d71aca53e4af2e589681a2e63347c915ff472bfb
Change-Id: I1d4f8fc8c7c4f9638dffda0b8d8a9c70d5f95e4a
1 file changed
tree: cc5bb1effc4b322537c823901cb048a03a91f66b
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. flower
  6. jiri.lock
  7. MILESTONE
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. 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.