[roll] Roll fuchsia [starnix] Refactor rename locking using RenameContext Introduce RenameContext to encapsulate parent write guards and child nodes involved in a rename/exchange operation. This simplifies the FileSystemOps::rename and exchange APIs by moving the locking logic (which now locks parent node info in hierarchical order) and cycle checks into the VFS, preventing LockDep deadlocks. Original-Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1638635 Original-Original-Revision: 41e4a28eb153b0fc2b04a865be7314e264b57916 GitOrigin-RevId: a29d79c2de12145dd3cab7c81bb3ea63f335dbdd Change-Id: I2671005e7ea2b9d3f44169079ebd2bc6347e86fd Reviewed-on: https://fuchsia-review.googlesource.com/c/integration/+/1641045 Cr-Commit-Position: refs/heads/main@{#194246}
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.