)]}'
{
  "commit": "60f355ead31e2be8d06ac8acb163df91a1c64e3b",
  "tree": "11a011cb6bcbf4adc27b871556a6d475b6826dd3",
  "parents": [
    "c58098be979509a54021e837a47fcad08db31f94"
  ],
  "author": {
    "name": "Mikulas Patocka",
    "email": "mpatocka@redhat.com",
    "time": "Thu Dec 10 23:52:05 2009 +0000"
  },
  "committer": {
    "name": "Alasdair G Kergon",
    "email": "agk@redhat.com",
    "time": "Thu Dec 10 23:52:05 2009 +0000"
  },
  "message": "dm raid1: hold write bios when errors are handled\n\nHold all write bios when errors are handled.\n\nPreviously the failures list was used only when handling errors with\na userspace daemon such as dmeventd.  Now, it is always used for all bios.\nThe regions where some writes failed must be marked as nosync. This can only\nbe done in process context (i.e. in raid1 workqueue), not in the\nwrite_callback function.\n\nPreviously the write would succeed if writing to at least one leg\nsucceeded.  This is wrong because data from the failed leg may be\nreplicated to the correct leg.  Now, if using a userspace daemon, the\nwrite with some failures will be held until the daemon has done its job\nand reconfigured the array.  If not using a daemon, the write still\nsucceeds if at least one leg succeeds. This is bad, but it is consistent\nwith current behavior.\n\nSigned-off-by: Mikulas Patocka \u003cmpatocka@redhat.com\u003e\nReviewed-by: Takahiro Yasui \u003ctyasui@redhat.com\u003e\nTested-by: Takahiro Yasui \u003ctyasui@redhat.com\u003e\nSigned-off-by: Alasdair G Kergon \u003cagk@redhat.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "4f466ad75680f2d430533f3100d9f21e62ec0b0f",
      "old_mode": 33188,
      "old_path": "drivers/md/dm-raid1.c",
      "new_id": "e363335e8d8147d6ffb16fbc2c9f32f3e87b36d2",
      "new_mode": 33188,
      "new_path": "drivers/md/dm-raid1.c"
    }
  ]
}