From: Ritesh Harjani (IBM) Date: Fri, 23 Jan 2026 06:33:00 +0000 (+0800) Subject: iomap: Fix possible overflow condition in iomap_write_delalloc_scan X-Git-Tag: v6.1.162~22 X-Git-Url: http://git.ipfire.org/gitweb/?a=commitdiff_plain;h=0c6cf409093f307ee05114f834516730c0da5b21;p=thirdparty%2Fkernel%2Fstable.git iomap: Fix possible overflow condition in iomap_write_delalloc_scan [ Upstream commit eee2d2e6ea5550118170dbd5bb1316ceb38455fb ] folio_next_index() returns an unsigned long value which left shifted by PAGE_SHIFT could possibly cause an overflow on 32-bit system. Instead use folio_pos(folio) + folio_size(folio), which does this correctly. Suggested-by: Matthew Wilcox Signed-off-by: Ritesh Harjani (IBM) Reviewed-by: Darrick J. Wong Signed-off-by: Rajani Kantha <681739313@139.com> Signed-off-by: Greg Kroah-Hartman --- diff --git a/fs/iomap/buffered-io.c b/fs/iomap/buffered-io.c index 70e246f7e8fe8..e4f58d1e12d48 100644 --- a/fs/iomap/buffered-io.c +++ b/fs/iomap/buffered-io.c @@ -903,7 +903,7 @@ static int iomap_write_delalloc_scan(struct inode *inode, * the end of this data range, not the end of the folio. */ *punch_start_byte = min_t(loff_t, end_byte, - folio_next_index(folio) << PAGE_SHIFT); + folio_pos(folio) + folio_size(folio)); } /* move offset to start of next folio in range */