iomap: Lift blocksize restriction on atomic writes
authorRitesh Harjani (IBM) <ritesh.list@gmail.com>
Mon, 3 Mar 2025 17:11:14 +0000 (17:11 +0000)
committerChristian Brauner <brauner@kernel.org>
Thu, 6 Mar 2025 10:00:12 +0000 (11:00 +0100)
commit786e3080cbe916f6a4c0987124d4f930c1814a97
treede135086708083b658030fa37321bd5616acd373
parent794ca29dcc924cd3f16d12b6fba61074c992b8fd
iomap: Lift blocksize restriction on atomic writes

Filesystems like ext4 can submit writes in multiples of blocksizes.
But we still can't allow the writes to be split. Hence let's check if
the iomap_length() is same as iter->len or not.

It is the role of the FS to ensure that a single mapping may be created
for an atomic write. The FS will also continue to check size and alignment
legality.

Signed-off-by: "Ritesh Harjani (IBM)" <ritesh.list@gmail.com>
jpg: Tweak commit message
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
Signed-off-by: John Garry <john.g.garry@oracle.com>
Link: https://lore.kernel.org/r/20250303171120.2837067-7-john.g.garry@oracle.com
Signed-off-by: Christian Brauner <brauner@kernel.org>
fs/iomap/direct-io.c