)]}'
{
  "commit": "dee06946e08bbfe7a41cdaa8853673586d5f63e2",
  "tree": "a0d8d38f4a1605849d27f6b0640a4151cdcc741d",
  "parents": [
    "b0138761c306ce7ed80dd471d727d247e4813ec0"
  ],
  "author": {
    "name": "Charles Celerier",
    "email": "chcl@fuchsia.infra.roller.google.com",
    "time": "Thu Sep 08 17:38:26 2022 +0000"
  },
  "committer": {
    "name": "Copybara-Service",
    "email": "copybara-worker@google.com",
    "time": "Thu Sep 08 10:40:04 2022 -0700"
  },
  "message": "[roll] Roll fuchsia Revert \"[kernel] Use PinnedVmObject::reset instead of ktl::move\"\n\nThis reverts commit fd979cbb7a73a2ff2be8d601c9d4f36c3a03eb7d.\n\nReason for revert: Suspected cause of https://fxbug.dev/108834.\n\nOriginal change\u0027s description:\n\u003e [kernel] Use PinnedVmObject::reset instead of ktl::move\n\u003e\n\u003e We\u0027re relying on ktl::move to run the destructor of PinnedVmObject\n\u003e ignoring the result value, but this is triggering an error in the\n\u003e tip-of-tree Clang:\n\u003e\n\u003e         ktl::move(data-\u003epinned_buffer);\n\u003e         ^~~~~~~~~ ~~~~~~~~~~~~~~~~~~~\n\u003e     1 error generated.\n\u003e\n\u003e Use PinnedVmObject::reset instead which has the same effect.\n\u003e\n\u003e Original-Fixed: 108702\n\u003e Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/720210\n\nOriginal-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/722531\nOriginal-Revision: 0c54daca5e6dbd4ff52ed5de1ee81443a4fe724d\nGitOrigin-RevId: d7098d4ec538197fde9fc6701881eb8693c3b4c3\nChange-Id: I08d086ba245525df82e4a65e745022d3bd5cccb9\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "c46e238f8d1784dee50d79248b8629217f27b995",
      "old_mode": 33188,
      "old_path": "stem",
      "new_id": "d695ef0ee1446145a8a468cc1e354eaa43c6d407",
      "new_mode": 33188,
      "new_path": "stem"
    }
  ]
}