Unverified Commit 786e3080 authored by Ritesh Harjani (IBM)'s avatar Ritesh Harjani (IBM) Committed by Christian Brauner
Browse files

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: default avatar"Ritesh Harjani (IBM)" <ritesh.list@gmail.com>
jpg: Tweak commit message
Reviewed-by: default avatar"Darrick J. Wong" <djwong@kernel.org>
Signed-off-by: default avatarJohn Garry <john.g.garry@oracle.com>
Link: https://lore.kernel.org/r/20250303171120.2837067-7-john.g.garry@oracle.com


Signed-off-by: default avatarChristian Brauner <brauner@kernel.org>
parent 794ca29d

fs/iomap/direct-io.c

+1 −1
Original line number Diff line number Diff line
@@ -351,7 +351,7 @@ static int iomap_dio_bio_iter(struct iomap_iter *iter, struct iomap_dio *dio) 
	u64 copied = 0;

	size_t orig_count;



	if (atomic_hw && length != fs_block_size)

	if (atomic_hw && length != iter->len)

		return -EINVAL;



	if ((pos | length) & (bdev_logical_block_size(iomap->bdev) - 1) ||