)]}'
{
  "commit": "307615a26e95406c42c95916a66ba50434567e0f",
  "tree": "3fcb794cbd50958839c955ec492b3fb25fd801b6",
  "parents": [
    "979570e02981d4a8fc20b3cc8fd651856c98ee9d"
  ],
  "author": {
    "name": "Mike Snitzer",
    "email": "snitzer@redhat.com",
    "time": "Wed Sep 26 23:45:39 2012 +0100"
  },
  "committer": {
    "name": "Alasdair G Kergon",
    "email": "agk@redhat.com",
    "time": "Wed Sep 26 23:45:39 2012 +0100"
  },
  "message": "dm thin: do not set discard_zeroes_data\n\nThe dm thin pool target claims to support the zeroing of discarded\ndata areas.  This turns out to be incorrect when processing discards\nthat do not exactly cover a complete number of blocks, so the target\nmust always set discard_zeroes_data_unsupported.\n\nThe thin pool target will zero blocks when they are allocated if the\nskip_block_zeroing feature is not specified.  The block layer\nmay send a discard that only partly covers a block.  If a thin pool\nblock is partially discarded then there is no guarantee that the\ndiscarded data will get zeroed before it is accessed again.\nDue to this, thin devices cannot claim discards will always zero data.\n\nSigned-off-by: Mike Snitzer \u003csnitzer@redhat.com\u003e\nSigned-off-by: Joe Thornber \u003cejt@redhat.com\u003e\nCc: stable@vger.kernel.org # 3.4+\nSigned-off-by: Alasdair G Kergon \u003cagk@redhat.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "af1fc3b2c2adbb365e247a2d45c1f7a94de9b6dd",
      "old_mode": 33188,
      "old_path": "drivers/md/dm-thin.c",
      "new_id": "d4209231069d2039db0210daabe7d19c9a8e866b",
      "new_mode": 33188,
      "new_path": "drivers/md/dm-thin.c"
    }
  ]
}