)]}'
{
  "commit": "3e802fc7c387b06b1f64e09ed90aaa7f99bbb5a8",
  "tree": "8a90eabd6b48a76143be19ba81d3eee8f1d08d7c",
  "parents": [
    "00dced3f673035b8522d20ebe7ab3b68de21d08a"
  ],
  "author": {
    "name": "Brian Foster",
    "email": "bfoster@redhat.com",
    "time": "Thu Aug 07 10:56:26 2025 -0400"
  },
  "committer": {
    "name": "Zorro Lang",
    "email": "zlang@kernel.org",
    "time": "Tue Aug 12 16:34:03 2025 +0800"
  },
  "message": "xfs: test iomap zero range via fsx and error tag\n\niomap supports a zero range operation based on buffered writes. This\nmechanism is used in limited spots, such as partial block zeroing,\netc., because usually for larger zeroing ops it is more efficient to\npunch a hole and allocate unwritten extents.\n\nThis means iomap zero range has limited production test coverage\neven though it has some particular corner cases that warrant test\ncoverage. XFS supports an error injection knob to force use of iomap\nzero range on fallocate zero range operations. Add a test to run fsx\nwith this knob enabled to provide more zeroing test coverage.\n\nSigned-off-by: Brian Foster \u003cbfoster@redhat.com\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n",
  "tree_diff": [
    {
      "type": "add",
      "old_id": "0000000000000000000000000000000000000000",
      "old_mode": 0,
      "old_path": "/dev/null",
      "new_id": "d135b4571466972bb971993e77149cdbe69ec15a",
      "new_mode": 33261,
      "new_path": "tests/xfs/131"
    },
    {
      "type": "add",
      "old_id": "0000000000000000000000000000000000000000",
      "old_mode": 0,
      "old_path": "/dev/null",
      "new_id": "2ca0d9325d671efcdba63accc0a437dd015081fd",
      "new_mode": 33188,
      "new_path": "tests/xfs/131.out"
    }
  ]
}