)]}'
{
  "commit": "506531905296d6aee84480c879b25ea98c3f9db6",
  "tree": "18549bd9c5724e1517b5497881adc000f21349fc",
  "parents": [
    "16780cabb877dbd0c8c5e9ff9bdebd6c5bdd1a7b"
  ],
  "author": {
    "name": "Chris Mason",
    "email": "chris.mason@oracle.com",
    "time": "Wed Feb 22 12:36:24 2012 -0500"
  },
  "committer": {
    "name": "Chris Mason",
    "email": "chris.mason@oracle.com",
    "time": "Thu Feb 23 10:43:45 2012 -0500"
  },
  "message": "Btrfs: clear the extent uptodate bits during parent transid failures\n\nIf btrfs reads a block and finds a parent transid mismatch, it clears\nthe uptodate flags on the extent buffer, and the pages inside it.  But\nwe only clear the uptodate bits in the state tree if the block straddles\nmore than one page.\n\nThis is from an old optimization from to reduce contention on the extent\nstate tree.  But it is buggy because the code that retries a read from\na different copy of the block is going to find the uptodate state bits\nset and skip the IO.\n\nThe end result of the bug is that we\u0027ll never actually read the good\ncopy (if there is one).\n\nThe fix here is to always clear the uptodate state bits, which is safe\nbecause this code is only called when the parent transid fails.\n\nSigned-off-by: Chris Mason \u003cchris.mason@oracle.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "45ca8f9b0d612f3ec08e34004f2095b3dd035d1c",
      "old_mode": 33188,
      "old_path": "fs/btrfs/extent_io.c",
      "new_id": "a55fbe6252ded4e41d9b76cb3bed1a9f98acd065",
      "new_mode": 33188,
      "new_path": "fs/btrfs/extent_io.c"
    }
  ]
}