summaryrefslogtreecommitdiff
path: root/scripts/Makefile.thinlto
diff options
context:
space:
mode:
authorChristian Brauner <brauner@kernel.org>2026-07-27 11:43:15 +0200
committerChristian Brauner <brauner@kernel.org>2026-07-27 11:43:15 +0200
commitd5c57d9bf03516d625521cd6cf5acfd93e3e63c7 (patch)
tree2ea9342d51073b860f44ad40301448314cc344af /scripts/Makefile.thinlto
parent1590cf0329716306e948a8fc29f1d3ee87d3989f (diff)
parentb924d8d4e54f179bccd9f28f57a2c4fbb570c04a (diff)
downloadlinux-next-d5c57d9bf03516d625521cd6cf5acfd93e3e63c7.tar.gz
linux-next-d5c57d9bf03516d625521cd6cf5acfd93e3e63c7.zip
Merge patch series "nilfs2: convert O_DIRECT reads to iomap"
Viacheslav Dubeyko <slava@dubeyko.com> says: This series removes NILFS2 using of blockdev_direct_IO() by converting the O_DIRECT read path to iomap. NILFS2 is a log-structured, copy-on-write filesystem, which makes it a poor fit for a full iomap conversion. Newly allocated blocks are delay-allocated by nilfs_get_block() and only receive a real disk address when the segment constructor writes them out as part of a log. The segment constructor walks buffer_head lists directly and is not integrated with the generic address_space writeback path. First patch adds a new, read-only nilfs_iomap_ops wrapping the existing nilfs_bmap_lookup_contig() lookup. The second patch wires that ops table into O_DIRECT reads via iomap_dio_rw(), sets FMODE_CAN_ODIRECT explicitly on open, and removes nilfs_direct_IO() and the .direct_IO callback entirely. O_DIRECT writes are explicitly downgraded to the ordinary buffered write path in nilfs_file_write_iter(). * patches from https://patch.msgid.link/20260724222745.2107464-1-slava@dubeyko.com: nilfs2: switch O_DIRECT reads to iomap nilfs2: add iomap operations for direct I/O reads Link: https://patch.msgid.link/20260724222745.2107464-1-slava@dubeyko.com Signed-off-by: Christian Brauner (Amutable) <brauner@kernel.org>
Diffstat (limited to 'scripts/Makefile.thinlto')
0 files changed, 0 insertions, 0 deletions