)]}'
{
  "commit": "5f91bb050ecc4ff1d8d3d07edbe550c8f431c5e1",
  "tree": "7aa9e70ef2432d702ada2fac12026de8bfb35405",
  "parents": [
    "edced191e4512b7795380563634f4d44b21c684a"
  ],
  "author": {
    "name": "Michael Reed",
    "email": "mdr@sgi.com",
    "time": "Mon Aug 10 11:59:28 2009 -0500"
  },
  "committer": {
    "name": "James Bottomley",
    "email": "James.Bottomley@suse.de",
    "time": "Sat Aug 22 17:52:22 2009 -0500"
  },
  "message": "[SCSI] reservation conflict after timeout causes device to be taken offline\n\nAn IBM tape drive failed to complete a PERSISTENT RESERVE IN within the scsi\ncmd timeout.  Error recovery was initiated and it sequenced from abort through\ntaking the tape drive offline.\n\nThe device was taken offline because it repeatedly responded to the TUR command\nissued by error recovery with a RESERVATION CONFLICT status.  The tape drive\nwas reserved to another system.  This is perfectly legitimate response to TUR,\nand is one that an escalation of recovery is unlikely to clear.  Further,\nescalation of recovery can have undesirable side effects on the operation of\ntape drives shared with other initiators.\n\nInstead of escalating recovery, error recovery should treat the RESERVATION\nCONFLICT response to the TUR as a good status, giving the issuer of the\ncommand the opportunity to handle the timeout and reservation conflict.\n\nSigned-off-by: Michael reed \u003cmdr@sgi.com\u003e\nSigned-off-by: James Bottomley \u003cJames.Bottomley@suse.de\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "a1689353d7fd715cf91776e9b290381795876477",
      "old_mode": 33188,
      "old_path": "drivers/scsi/scsi_error.c",
      "new_id": "877204daf549644338fb2b55494944af7127a8ea",
      "new_mode": 33188,
      "new_path": "drivers/scsi/scsi_error.c"
    }
  ]
}