)]}'
{
  "commit": "ca57558daefe374a04bfceee5780c5765382e041",
  "tree": "764930017d575cd19a02704662a7cf67adb33f2e",
  "parents": [
    "86950a4e23c176d88b27cfd06039bb4d88b520ff"
  ],
  "author": {
    "name": "Darrick J. Wong",
    "email": "djwong@kernel.org",
    "time": "Tue Jul 29 13:09:17 2025 -0700"
  },
  "committer": {
    "name": "Zorro Lang",
    "email": "zlang@kernel.org",
    "time": "Sat Aug 02 22:15:17 2025 +0800"
  },
  "message": "generic/767: only test the hardware atomic write unit\n\nThis test sets up scsi_debug so that we can test the fs and block layer\ncode for hardware-accelerated atomic writes (and not just a software\nfallback).  However, the userspace ABI for detecting atomic write\ngeometry has changed since the start of development (to include said\nsoftware fallback) so we must add some extra code to find the real\nhardware capabilities, and base the write sizes based on that.\n\nThis fixes a test failure with 32k blocksizes because the advertised\natomic_write_unit_max is 128M and fallocate quickly runs out of space.\n\nWhile we\u0027re at it fix a stupid variable usage bug in the loop.\n\nCc: fstests@vger.kernel.org # v2025.07.13\nFixes: fa8694c823d853 (\"generic: various atomic write tests with hardware and scsi_debug\")\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "95d545a67cadda32c3f06a5e58eee6a2edf740dc",
      "old_mode": 33188,
      "old_path": "common/atomicwrites",
      "new_id": "33526399d2e980fc7fb639afa8fa767fcffd4321",
      "new_mode": 33188,
      "new_path": "common/atomicwrites"
    },
    {
      "type": "modify",
      "old_id": "31d599eacfd63b2bafce51cbd99d5f74ad7c2378",
      "old_mode": 33261,
      "old_path": "tests/generic/767",
      "new_id": "161fef03825db4c22d545cc1282d1695c50b82dd",
      "new_mode": 33261,
      "new_path": "tests/generic/767"
    }
  ]
}