)]}'
{
  "commit": "5279efebcf8f8fbf2ed2feed63cdb9d375c7cd07",
  "tree": "d2118bda8416c830f444fc21ca671c73e2c2a11e",
  "parents": [
    "fa500928ad9da6dd570918e3dfca13c029af07a8"
  ],
  "author": {
    "name": "Jeff Cody",
    "email": "jcody@redhat.com",
    "time": "Thu Oct 01 00:06:37 2015 -0400"
  },
  "committer": {
    "name": "Jeff Cody",
    "email": "jcody@redhat.com",
    "time": "Thu Oct 01 15:02:21 2015 -0400"
  },
  "message": "block: mirror - fix full sync mode when target does not support zero init\n\nDuring mirror, if the target device does not support zero init, a\nmirror may result in a corrupted image for sync\u003d\"full\" mode.\n\nThis is due to how the initial dirty bitmap is set up prior to copying\ndata - we did not mark sectors as dirty that are unallocated.  This\nmeans those unallocated sectors are skipped over on the target, and for\na device without zero init, invalid data may reside in those holes.\n\nIf both of the following conditions are true, then we will explicitly\nmark all sectors as dirty:\n\n    1.) sync \u003d \"full\"\n    2.) bdrv_has_zero_init(target) \u003d\u003d false\n\nIf the target does support zero init, but a target image is passed in\nwith data already present (i.e. an \"existing\" image), it is assumed the\ndata present in the existing image is valid data for those sectors.\n\nReviewed-by: Paolo Bonzini \u003cpbonzini@redhat.com\u003e\nMessage-id: 91ed4bc5bda7e2b09eb508b07c83f4071fe0b3c9.1443705220.git.jcody@redhat.com\nSigned-off-by: Jeff Cody \u003cjcody@redhat.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "a2589261f58bf5456e8e210924e6c8517db70829",
      "old_mode": 33188,
      "old_path": "block/mirror.c",
      "new_id": "87928aba840e369ac663f7ade3e5ed00d5663f1b",
      "new_mode": 33188,
      "new_path": "block/mirror.c"
    }
  ]
}