)]}'
{
  "commit": "7ca78d57d11a91bc93b35342fa58647b85bedeb1",
  "tree": "398f2f91e5252b45872506763ae3677e1f35c026",
  "parents": [
    "78d7f5f726deb562a51126603f2dc5d00990b223"
  ],
  "author": {
    "name": "NeilBrown",
    "email": "neilb@suse.de",
    "time": "Wed May 11 14:50:37 2011 +1000"
  },
  "committer": {
    "name": "NeilBrown",
    "email": "neilb@suse.de",
    "time": "Wed May 11 14:50:37 2011 +1000"
  },
  "message": "md/raid1: try fix_sync_read_error before process_checks.\n\nIf we get a read error during resync/recovery we current repeat with\nsingle-page reads to find out just where the error is, and possibly\nread each page from a different device.\n\nWith check/repair we don\u0027t currently do that, we just fail.\nHowever it is possible that while all devices fail on the large 64K\nread, we might be able to satisfy each 4K from one device or another.\n\nSo call fix_sync_read_error before process_checks to maximise the\nchance of finding good data and writing it out to the devices with\nread errors.\n\nFor this to work, we need to set the \u0027uptodate\u0027 flags properly after\nfix_sync_read_error has succeeded.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "2b9e86ceaf2ff4522a77547f750b9ff84f33a854",
      "old_mode": 33188,
      "old_path": "drivers/md/raid1.c",
      "new_id": "b9d6da1272f12d2bfc2b6b860d772ba543e8768f",
      "new_mode": 33188,
      "new_path": "drivers/md/raid1.c"
    }
  ]
}