From: Joanne Koong <joannelkoong@gmail.com>
To: Christian Brauner <brauner@kernel.org>
Cc: linux-fsdevel@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
"Darrick J . Wong" <djwong@kernel.org>,
changfengnan@bytedance.com, kbusch@kernel.org,
Matthew Wilcox <willy@infradead.org>, Jan Kara <jack@suse.cz>,
Jonathan Corbet <corbet@lwn.net>, David Sterba <dsterba@suse.com>,
Gao Xiang <xiang@kernel.org>, Namjae Jeon <linkinjeon@kernel.org>,
Theodore Ts'o <tytso@mit.edu>, Jaegeuk Kim <jaegeuk@kernel.org>,
Miklos Szeredi <miklos@szeredi.hu>,
Andreas Gruenbacher <agruenba@redhat.com>,
Mikulas Patocka <mikulas@artax.karlin.mff.cuni.cz>,
Hyunchul Lee <hyc.lee@gmail.com>,
Konstantin Komarov <almaz.alexandrovich@paragon-software.com>,
Carlos Maiolino <cem@kernel.org>,
Damien Le Moal <dlemoal@kernel.org>,
libaokun@linux.alibaba.com, bfoster@redhat.com,
linux-ext4@vger.kernel.org, linux-xfs@vger.kernel.org,
Viacheslav Dubeyko <slava@dubeyko.com>,
Ryusuke Konishi <konishi.ryusuke@gmail.com>,
linux-nilfs@vger.kernel.org, fuse-devel@lists.linux.dev,
Zhang Yi <yi.zhang@huawei.com>
Subject: [PATCH 0/5] iomap: remaining patches for iomap_iter_next conversion
Date: Tue, 27 Oct 2026 14:53:21 -0700 [thread overview]
Message-ID: <20261027215326.2693300-1-joannelkoong@gmail.com> (raw)
Hi Christian,
This is a resend of the last 3 patches from the "iomap: convert to in-iter
iomap_next() model" patch series [1].
Those 3 patches are rebased on top of current mainline (commit 83f32c773255
("Merge tag 'erofs-for-7.4-rc1-2' ...")) in Linus's tree. They require two new
preparatory patches (patches 1 and 2 in this series), which are trivial
->iomap_next() conversions of the nilfs2 and fuse iomap code that was added
during this merge window. There were conflicts with "iomap: pass
iomap_iter_next_fn directly instead of struct iomap_ops" (patch 4 in this
series) during the rebase. These are resolved in the patch, which now also
converts the iomap users added this merge window (ext4 iomap buffered I/O,
exfat swap activation, nilfs2, and fuse ext_map). Jan's Acked-by and
Christoph's Reviewed-by on it predate these changes.
These patches are being sent out now in case anyone wants to look at the
preparatory patches or patch 4. This series applies cleanly to both current
mainline and next-20261027. If anything conflicts by the time you pick it up
at the end of the merge window, I'll rebase and resend.
Thanks,
Joanne
[1] https://lore.kernel.org/linux-fsdevel/20260729192737.3190206-1-joannelkoong@gmail.com/
Joanne Koong (5):
nilfs2: convert iomap ops to ->iomap_next()
fuse: convert ext_map iomap ops to ->iomap_next()
iomap: remove ->iomap_begin()/->iomap_end() legacy path
iomap: pass iomap_iter_next_fn directly instead of struct iomap_ops
Documentation: iomap: update docs to reflect iomap_iter_next model
Documentation/filesystems/iomap/design.rst | 140 +++++++++++++-----
.../filesystems/iomap/operations.rst | 68 ++++-----
Documentation/filesystems/iomap/porting.rst | 16 +-
block/fops.c | 10 +-
fs/btrfs/direct-io.c | 8 +-
fs/dax.c | 48 +++---
fs/erofs/data.c | 28 ++--
fs/erofs/internal.h | 3 +-
fs/erofs/zmap.c | 7 +-
fs/exfat/file.c | 14 +-
fs/exfat/inode.c | 6 +-
fs/exfat/iomap.c | 22 +--
fs/exfat/iomap.h | 6 +-
fs/ext2/ext2.h | 3 +-
fs/ext2/file.c | 4 +-
fs/ext2/inode.c | 9 +-
fs/ext4/ext4.h | 10 +-
fs/ext4/extents.c | 8 +-
fs/ext4/file.c | 22 +--
fs/ext4/inode.c | 58 +++-----
fs/f2fs/data.c | 6 +-
fs/f2fs/f2fs.h | 3 +-
fs/f2fs/file.c | 4 +-
fs/fuse/dax.c | 10 +-
fs/fuse/ext_map.c | 11 +-
fs/fuse/file.c | 10 +-
fs/fuse/virtio_fs.c | 3 +-
fs/gfs2/aops.c | 6 +-
fs/gfs2/bmap.c | 9 +-
fs/gfs2/bmap.h | 2 +-
fs/gfs2/file.c | 6 +-
fs/gfs2/inode.c | 6 +-
fs/hpfs/file.c | 6 +-
fs/internal.h | 1 -
fs/iomap/buffered-io.c | 40 ++---
fs/iomap/direct-io.c | 8 +-
fs/iomap/fiemap.c | 8 +-
fs/iomap/iter.c | 13 +-
fs/iomap/seek.c | 8 +-
fs/iomap/swapfile.c | 4 +-
fs/iomap/trace.h | 12 +-
fs/nilfs2/file.c | 2 +-
fs/nilfs2/iomap.c | 4 +-
fs/nilfs2/iomap.h | 4 +-
fs/ntfs/aops.c | 6 +-
fs/ntfs/file.c | 20 +--
fs/ntfs/inode.c | 2 +-
fs/ntfs/iomap.c | 42 ++----
fs/ntfs/iomap.h | 10 +-
fs/ntfs3/file.c | 16 +-
fs/ntfs3/inode.c | 13 +-
fs/ntfs3/ntfs_fs.h | 3 +-
fs/remap_range.c | 6 +-
fs/xfs/xfs_aops.c | 8 +-
fs/xfs/xfs_file.c | 53 +++----
fs/xfs/xfs_iomap.c | 55 ++-----
fs/xfs/xfs_iomap.h | 16 +-
fs/xfs/xfs_iops.c | 4 +-
fs/xfs/xfs_reflink.c | 6 +-
fs/zonefs/file.c | 22 +--
include/linux/dax.h | 18 +--
include/linux/fs.h | 7 +-
include/linux/iomap.h | 66 +++++----
63 files changed, 492 insertions(+), 557 deletions(-)
--
2.52.0
next reply other threads:[~2026-10-27 21:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 21:53 Joanne Koong [this message]
2026-10-27 21:53 ` [PATCH 1/5] nilfs2: convert iomap ops to ->iomap_next() Joanne Koong
2026-10-27 22:03 ` sashiko-bot
2026-10-28 15:00 ` Christoph Hellwig
2026-10-28 16:17 ` Ryusuke Konishi
2026-10-27 21:53 ` [PATCH 2/5] fuse: convert ext_map " Joanne Koong
2026-10-27 22:02 ` sashiko-bot
2026-10-28 15:01 ` Christoph Hellwig
2026-10-27 21:53 ` [PATCH 3/5] iomap: remove ->iomap_begin()/->iomap_end() legacy path Joanne Koong
2026-10-27 22:04 ` sashiko-bot
2026-10-27 21:53 ` [PATCH 4/5] iomap: pass iomap_iter_next_fn directly instead of struct iomap_ops Joanne Koong
2026-10-27 22:06 ` sashiko-bot
2026-10-27 21:53 ` [PATCH 5/5] Documentation: iomap: update docs to reflect iomap_iter_next model Joanne Koong
2026-10-27 22:07 ` sashiko-bot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261027215326.2693300-1-joannelkoong@gmail.com \
--to=joannelkoong@gmail.com \
--cc=agruenba@redhat.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=bfoster@redhat.com \
--cc=brauner@kernel.org \
--cc=cem@kernel.org \
--cc=changfengnan@bytedance.com \
--cc=corbet@lwn.net \
--cc=djwong@kernel.org \
--cc=dlemoal@kernel.org \
--cc=dsterba@suse.com \
--cc=fuse-devel@lists.linux.dev \
--cc=hch@lst.de \
--cc=hyc.lee@gmail.com \
--cc=jack@suse.cz \
--cc=jaegeuk@kernel.org \
--cc=kbusch@kernel.org \
--cc=konishi.ryusuke@gmail.com \
--cc=libaokun@linux.alibaba.com \
--cc=linkinjeon@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nilfs@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=mikulas@artax.karlin.mff.cuni.cz \
--cc=slava@dubeyko.com \
--cc=tytso@mit.edu \
--cc=willy@infradead.org \
--cc=xiang@kernel.org \
--cc=yi.zhang@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox