[roll] Roll fuchsia [starnix][vfs] Reset dependencies on parents in rename

Reset the lock dependencies on `old_parent` and `new_parent`
at the end of `DirEntry::rename`.

`ordered_write_lock` locks `old_parent` and `new_parent` by
memory address to avoid deadlocks between independent
directories. However, this dynamically chosen lock order
can establish a reverse edge to the hierarchical parent -> child
locking order in the global `tracing-mutex` graph.

If a subsequent rename replaces a child within these
directories, a false-positive lock cycle can be detected.
Clearing the dependency graph for the parent locks prevents
these false-positive cycle panics from `tracing-mutex`.

Original-Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1657714
Original-Original-Revision: d81c6477bc6bc76d7e20108363fcd16b9544f809
GitOrigin-RevId: 1d9249ce9d70e00d8740f5d18decc37ae4eb95d7
Change-Id: I0f7c734e4c35876a84a4b69d206b6a1f6a1b73db
Reviewed-on: https://fuchsia-review.googlesource.com/c/integration/+/1658145
Cr-Commit-Position: refs/heads/main@{#194818}
1 file changed
tree: 0cf0f86944ea16a0f2dbb8239326403fa713ad0c
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cobalt
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. 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.