[roll] Roll fuchsia [starnix] Fix vmsplice decoupling on munmap Avoid decoupling file-backed and shared memory mappings from their backing VMOs when they are unmapped while in a pipe (via vmsplice). Previously, Starnix aggressively snapshotted all vmspliced payloads on munmap. This broke Linux compatibility for file-backed mappings, where subsequent writes to the file (e.g., via pwrite) should remain visible to the pipe reader even after the mapping is unmapped. Now, we only snapshot (decouple) private anonymous mappings to allow resource reclamation, while keeping file-backed and shared mappings coupled to their source VMOs. Original-Original-Bug: 521345037 Test: vmsplice_test Original-Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1649354 Original-Original-Revision: 7ee937e49103934603a89a0c7c71783dab4fbe44 GitOrigin-RevId: fefd2afe3568d14e4ab5ee328b2a5254023145d0 Change-Id: I94e1ca3bbed30b6f0b161ff0b6ef3139aa3b0601 Reviewed-on: https://fuchsia-review.googlesource.com/c/integration/+/1653381 Cr-Commit-Position: refs/heads/main@{#194688}
This repository contains Fuchsia's Global Integration manifest files.
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.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.