)]}'
{
  "commit": "da5d76b3e12abf0d78ed776146d7e7fb6f94de96",
  "tree": "be0cfedf6ce05370cb88675750cfd27ec985b658",
  "parents": [
    "93ab5b9771768dc99cef9550a75f74c5948eac0d"
  ],
  "author": {
    "name": "Sarthak Killedar",
    "email": "sarthak.killedar@gmail.com",
    "time": "Tue Aug 25 23:59:59 2026 +0000"
  },
  "committer": {
    "name": "Sarthak Killedar",
    "email": "sarthak.killedar@gmail.com",
    "time": "Tue Aug 25 23:59:59 2026 +0000"
  },
  "message": "verify: dump the received buffer when zero verify fails\n\nverify_zero() logs the file, offset and length of a mismatch, but unlike\nthe header and pattern verify paths it never writes out the data it read.\nThat makes trim_verify_zero and write zeroes verify failures harder to\nanalyze than a regular verify failure, where verify_dump\u003d1 leaves the\noffending block on disk for inspection.\n\nDump the received block from verify_zero() when verify_dump is set, so\nthat both callers benefit. There is no point in also dumping an expected\nbuffer, as the expected contents are all zeroes.\n\nSigned-off-by: Sarthak Killedar \u003csarthak.killedar@gmail.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "633a9bb24a49242645a920ab19e381b2fa07a02d",
      "old_mode": 33188,
      "old_path": "verify.c",
      "new_id": "a978aff07b1c228400668623aafe5ae3d84c79ae",
      "new_mode": 33188,
      "new_path": "verify.c"
    }
  ]
}