)]}'
{
  "commit": "8f6d90a0eb4dd843674300ea8e247208366391d4",
  "tree": "125820b53b7faf4d397b2c15bdd335345c506622",
  "parents": [
    "827e87e35bafaca3c0f7ace30be27c516aa978cc"
  ],
  "author": {
    "name": "Christoph Hellwig",
    "email": "hch@lst.de",
    "time": "Wed Nov 20 16:19:25 2024 -0800"
  },
  "committer": {
    "name": "Darrick J. Wong",
    "email": "djwong@kernel.org",
    "time": "Sun Nov 24 21:06:09 2024 -0800"
  },
  "message": "iomap: add a merge boundary flag\n\nFile systems might have boundaries over which merges aren\u0027t possible.\nIn fact these are very common, although most of the time some kind of\nheader at the beginning of this region (e.g. XFS alloation groups, ext4\nblock groups) automatically create a merge barrier.  But if that is\nnot present, say for a device purely used for data we need to manually\ncommunicate that to iomap.\n\nAdd a IOMAP_F_BOUNDARY flag to never merge I/O into a previous mapping.\n\nSigned-off-by: Christoph Hellwig \u003chch@lst.de\u003e\nReviewed-by: \"Darrick J. Wong\" \u003cdjwong@kernel.org\u003e\nSigned-off-by: \"Darrick J. Wong\" \u003cdjwong@kernel.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "ef0b68bccbb6126e136bffd3d6558a78bc8fc1e4",
      "old_mode": 33188,
      "old_path": "fs/iomap/buffered-io.c",
      "new_id": "fcadd31017d138a74b78c6c064e4158e265d378c",
      "new_mode": 33188,
      "new_path": "fs/iomap/buffered-io.c"
    },
    {
      "type": "modify",
      "old_id": "f61407e3b12192d78932d8c7ac737a5161da0bc9",
      "old_mode": 33188,
      "old_path": "include/linux/iomap.h",
      "new_id": "9ecb8ea7714cf99e5c22827923d090b3a8f6a601",
      "new_mode": 33188,
      "new_path": "include/linux/iomap.h"
    }
  ]
}