)]}'
{
  "commit": "d0e260782c3702a009645c3caa02e381dab8798b",
  "tree": "588f7776216df124d9372c7ced833b0bfb6d0a7f",
  "parents": [
    "a9366e61b03f55a6e009e687ad10e706714c9907"
  ],
  "author": {
    "name": "NeilBrown",
    "email": "neilb@suse.de",
    "time": "Tue Dec 01 17:30:59 2009 +1100"
  },
  "committer": {
    "name": "NeilBrown",
    "email": "neilb@suse.de",
    "time": "Tue Dec 01 17:30:59 2009 +1100"
  },
  "message": "md: revert incorrect fix for read error handling in raid1.\n\ncommit 4706b349f was a forward port of a fix that was needed\nfor SLES10.  But in fact it is not needed in mainline because\nthe earlier commit dd00a99e7a fixes the same problem in a\nbetter way.\nFurther, this commit introduces a bug in the way it interacts with\nthe automatic read-error-correction.  If, after a read error is\nsuccessfully corrected, the same disk is chosen to re-read - the\nre-read won\u0027t be attempted but an error will be returned instead.\n\nAfter reverting that commit, there is the possibility that a\nread error on a read-only array (where read errors cannot\nbe corrected as that requires a write) will repeatedly read the same\ndevice and continue to get an error.\nSo in the \"Array is readonly\" case, fail the drive immediately on\na read error.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\nCc: stable@kernel.org\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "a053423785c92e74256e4ad8e2aadc658538aee0",
      "old_mode": 33188,
      "old_path": "drivers/md/raid1.c",
      "new_id": "e07ce2e033a95c48ba2c9a78c519640743220e2d",
      "new_mode": 33188,
      "new_path": "drivers/md/raid1.c"
    }
  ]
}