)]}'
{
  "commit": "87d02f3e98a86abf70441b0a0418e01cb1d64b44",
  "tree": "e1e3824cdd59018b8e0dba7418da8f7fc1d21eab",
  "parents": [
    "99f7d39384d6f1967f3dddf27aca47280f63d8d7"
  ],
  "author": {
    "name": "Qu Wenruo",
    "email": "wqu@suse.com",
    "time": "Fri Oct 30 07:21:23 2026 +1030"
  },
  "committer": {
    "name": "Christian Brauner",
    "email": "brauner@kernel.org",
    "time": "Fri Oct 30 15:53:01 2026 +0100"
  },
  "message": "iomap: only follow dio alignment requirement if specified\n\nAfter commit 4025185cf953 (\"iomap: follow the alignment requirement for\niomap_dio_hole_iter()\"), generic/091 fails on both xfs and ext4.\n\nThe reason is that ext4 and xfs (except COW write) do not require full\nblock alignment for direct IO. They are totally fine reading a sub-block\nrange.\n\nThat commit fails any direct read of sub-block holes/prealloc, even those\nfilesystems can handle it without any problem.\n\nFix the regression by only follow the block alignment if the\nIOMAP_DIO_FSBLOCK_ALIGNED flag is set.\n\nFixes: 4025185cf953 (\"iomap: follow the alignment requirement for iomap_dio_hole_iter()\")\nReviewed-by: Pankaj Raghav(Samsung) \u003cpankaj.raghav@linux.dev\u003e\nSigned-off-by: Qu Wenruo \u003cwqu@suse.com\u003e\nLink: https://patch.msgid.link/0e89c49b6f7804081f4041007b81ac620a153830.1793307063.git.wqu@suse.com\nSigned-off-by: Christian Brauner (Amutable) \u003cbrauner@kernel.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "45bb24934f3d2d52966458fd53de642b4f6f1805",
      "old_mode": 33188,
      "old_path": "fs/iomap/direct-io.c",
      "new_id": "ad041ac3252a57ad3d8acd19bdeb9b69bd5d13a6",
      "new_mode": 33188,
      "new_path": "fs/iomap/direct-io.c"
    },
    {
      "type": "modify",
      "old_id": "59718f73c15a039bdff04fb47cd7d6ec494ae012",
      "old_mode": 33188,
      "old_path": "include/linux/iomap.h",
      "new_id": "5254430844b2c04dedcadcaab8f9918821d982e9",
      "new_mode": 33188,
      "new_path": "include/linux/iomap.h"
    }
  ]
}