)]}'
{
  "commit": "3a3a5ddb7a0f43c3dd0f98673f3d930a456725f8",
  "tree": "fa1e33c011c9f6350ce5118b89deafacbb1e0f2b",
  "parents": [
    "da5cabf80e2433131bf0ed8993abc0f7ea618c73"
  ],
  "author": {
    "name": "NeilBrown",
    "email": "neilb@suse.de",
    "time": "Mon Aug 16 18:09:31 2010 +1000"
  },
  "committer": {
    "name": "NeilBrown",
    "email": "neilb@suse.de",
    "time": "Wed Aug 18 11:39:38 2010 +1000"
  },
  "message": "Update recovery_offset even when external metadata is used.\n\nThe update of -\u003erecovery_offset in sync_sbs is appropriate even then external\nmetadata is in use.  However sync_sbs is only called when native\nmetadata is used.\n\nSo move that update in to the top of md_update_sb (which is the only\ncaller of sync_sbs) before the test on -\u003eexternal.\n\nThis moves the update out of -\u003ewrite_lock protection, but those fields\nonly need -\u003ereconfig_mutex protection which they still have.\n\nAlso move the test on -\u003epersistent up to where -\u003eexternal is set as\nfor metadata update purposes they are the same.\n\nClear MD_CHANGE_DEVS and MD_CHANGE_CLEAN as they can only be confusing\nif -\u003eexternal is set or -\u003epersistent isn\u0027t.\n\nFinally move the update of -\u003eutime down as it is only relevent (like\nthe -\u003eevents update) for native metadata.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\nReported-by: \"Kwolek, Adam\" \u003cadam.kwolek@intel.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "11567c7999a243d3d95ebecdb623c26de49705ce",
      "old_mode": 33188,
      "old_path": "drivers/md/md.c",
      "new_id": "c148b630215484f9689bf9257d6acf286685c37a",
      "new_mode": 33188,
      "new_path": "drivers/md/md.c"
    }
  ]
}