)]}'
{
  "commit": "2ac01520be8717f3492b10a083c3e0e22cb52cda",
  "tree": "cf39358b64bb3eb0d227db2b753d163f8012797a",
  "parents": [
    "3efffc3292d94271a15b1606b4a56adf6c6f04ed"
  ],
  "author": {
    "name": "Max Reitz",
    "email": "mreitz@redhat.com",
    "time": "Fri Sep 11 18:47:51 2015 +0200"
  },
  "committer": {
    "name": "Kevin Wolf",
    "email": "kwolf@redhat.com",
    "time": "Mon Sep 14 16:51:37 2015 +0200"
  },
  "message": "qcow2: Make qcow2_alloc_bytes() more explicit\n\nIn case of -EAGAIN returned by update_refcount(), we should discard the\ncluster offset we were trying to allocate and request a new one, because\nin theory that old offset might now be taken by a refcount block.\n\nIn practice, this was not the case due to update_refcount() generally\nreturning strictly monotonic increasing cluster offsets. However, this\nbehavior is not set in stone, and it is also not obvious when looking at\nqcow2_alloc_bytes() alone, so we should not rely on it.\n\nReported-by: Kevin Wolf \u003ckwolf@redhat.com\u003e\nSigned-off-by: Max Reitz \u003cmreitz@redhat.com\u003e\nSigned-off-by: Kevin Wolf \u003ckwolf@redhat.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "a49d59e71e80bfae330c4b4b8c24266535766769",
      "old_mode": 33188,
      "old_path": "block/qcow2-refcount.c",
      "new_id": "2110839da49783f642271c0feffee6bae9bd2ce4",
      "new_mode": 33188,
      "new_path": "block/qcow2-refcount.c"
    }
  ]
}