iomap: account for unaligned end offsets when truncating read range

Browse source

The end position to start truncating from may be at an offset into a
block, which under the current logic would result in overtruncation.

Adjust the calculation to account for unaligned end offsets.

Signed-off-by: Joanne Koong <joannelkoong@gmail.com>
Link: https://patch.msgid.link/20251111193658.3495942-3-joannelkoong@gmail.com
Reviewed-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
Signed-off-by: Christian Brauner <brauner@kernel.org>

...

This commit is contained in:

Joanne Koong 2025-11-11 11:36:51 -08:00 • committed by Christian Brauner

parent a0f1cabe29

commit 9d875e0eef

No known key found for this signature in database

GPG key ID: 91C61BC06578DCA2

1 changed files with 20 additions and 2 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

22

fs/iomap/buffered-io.c

View file