)]}'
{
  "commit": "888cdfae69fb5241db874823fa23fe91f932e2a7",
  "tree": "0cf0f86944ea16a0f2dbb8239326403fa713ad0c",
  "parents": [
    "223e14235d77767b4b4d7c07a1bd9faf55373f88"
  ],
  "author": {
    "name": "Benjamin Lerman",
    "email": "qsr@fuchsia.infra.roller.google.com",
    "time": "Mon Jun 15 14:32:32 2026 -0700"
  },
  "committer": {
    "name": "Copybara Service",
    "email": "copybara-worker@google.com",
    "time": "Mon Jun 15 14:32:32 2026 -0700"
  },
  "message": "[roll] Roll fuchsia [starnix][vfs] Reset dependencies on parents in rename\n\nReset the lock dependencies on `old_parent` and `new_parent`\nat the end of `DirEntry::rename`.\n\n`ordered_write_lock` locks `old_parent` and `new_parent` by\nmemory address to avoid deadlocks between independent\ndirectories. However, this dynamically chosen lock order\ncan establish a reverse edge to the hierarchical parent -\u003e child\nlocking order in the global `tracing-mutex` graph.\n\nIf a subsequent rename replaces a child within these\ndirectories, a false-positive lock cycle can be detected.\nClearing the dependency graph for the parent locks prevents\nthese false-positive cycle panics from `tracing-mutex`.\n\nOriginal-Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1657714\nOriginal-Original-Revision: d81c6477bc6bc76d7e20108363fcd16b9544f809\nGitOrigin-RevId: 1d9249ce9d70e00d8740f5d18decc37ae4eb95d7\nChange-Id: I0f7c734e4c35876a84a4b69d206b6a1f6a1b73db\nReviewed-on: https://fuchsia-review.googlesource.com/c/integration/+/1658145\nCr-Commit-Position: refs/heads/main@{#194818}\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "228bf4a901726ed7f6849ad23f566dc03394a2bd",
      "old_mode": 33188,
      "old_path": "stem",
      "new_id": "a81b50d6e8e914d38fc5017044daed08b28ee00b",
      "new_mode": 33188,
      "new_path": "stem"
    }
  ]
}