)]}'
{
  "commit": "1a855a0606653d2d82506281e2c686bacb4b2f45",
  "tree": "7eeca410e738491318c0d80bd0a0940c392e513f",
  "parents": [
    "a035fc3e2531703b539f23bec4ca7943cfc69349"
  ],
  "author": {
    "name": "NeilBrown",
    "email": "neilb@suse.de",
    "time": "Thu Dec 09 16:36:28 2010 +1100"
  },
  "committer": {
    "name": "NeilBrown",
    "email": "neilb@suse.de",
    "time": "Thu Dec 09 16:36:28 2010 +1100"
  },
  "message": "md: fix bug with re-adding of partially recovered device.\n\nWith v0.90 metadata, a hot-spare does not become a full member of the\narray until recovery is complete.  So if we re-add such a device to\nthe array, we know that all of it is as up-to-date as the event count\nwould suggest, and so it a bitmap-based recovery is possible.\n\nHowever with v1.x metadata, the hot-spare immediately becomes a full\nmember of the array, but it record how much of the device has been\nrecovered.  If the array is stopped and re-assembled recovery starts\nfrom this point.\n\nWhen such a device is hot-added to an array we currently lose the \u0027how\nmuch is recovered\u0027 information and incorrectly included it as a full\nin-sync member (after bitmap-based fixup).\nThis is wrong and unsafe and could corrupt data.\n\nSo be more careful about setting saved_raid_disk - which is what\nguides the re-adding of devices back into an array.\nThe new code matches the code in slot_store which does a similar\nthing, which is encouraging.\n\nThis is suitable for any -stable kernel.\n\nReported-by: \"Dailey, Nate\" \u003cNate.Dailey@stratus.com\u003e\nCc: stable@kernel.org\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "d66aaeddf95d7c14d16001a29e6e940c7adb5e6a",
      "old_mode": 33188,
      "old_path": "drivers/md/md.c",
      "new_id": "b757da1751805c72e79880af1f5bec83deb47558",
      "new_mode": 33188,
      "new_path": "drivers/md/md.c"
    }
  ]
}