)]}'
{
  "commit": "355840e7a7e56bb2834fd3b0da64da5465f8aeaa",
  "tree": "8ba816b2db3b96872f744c476c3d3d0d3f12fd23",
  "parents": [
    "bd860c53d4f9cad520d233e1ba690aaacfb39e9b"
  ],
  "author": {
    "name": "NeilBrown",
    "email": "neilb@suse.de",
    "time": "Wed Oct 26 10:31:04 2011 +1100"
  },
  "committer": {
    "name": "NeilBrown",
    "email": "neilb@suse.de",
    "time": "Wed Oct 26 10:31:04 2011 +1100"
  },
  "message": "md/raid5: fix bug that could result in reads from a failed device.\n\nThis bug was introduced in 415e72d034c50520ddb7ff79e7d1792c1306f0c9\nwhich was in 2.6.36.\n\nThere is a small window of time between when a device fails and when\nit is removed from the array.  During this time we might still read\nfrom it, but we won\u0027t write to it - so it is possible that we could\nread stale data.\n\nWe didn\u0027t need the test of \u0027Faulty\u0027 before because the test on\nIn_sync is sufficient.  Since we started allowing reads from the early\npart of non-In_sync devices we need a test on Faulty too.\n\nThis is suitable for any kernel from 2.6.36 onwards, though the patch\nmight need a bit of tweaking in 3.0 and earlier.\n\nCc: stable@kernel.org\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "eea9379f7faedb459b5581d06805701af89e662b",
      "old_mode": 33188,
      "old_path": "drivers/md/raid5.c",
      "new_id": "521bf2605f82e332aab6a5daac1206300f0a3d3f",
      "new_mode": 33188,
      "new_path": "drivers/md/raid5.c"
    }
  ]
}