* [PATCH 6.1.y] iomap: Fix possible overflow condition in iomap_write_delalloc_scan
@ 2026-01-23 6:33 Rajani Kantha
0 siblings, 0 replies; only message in thread
From: Rajani Kantha @ 2026-01-23 6:33 UTC (permalink / raw)
To: gregkh, ritesh.list, stable
Cc: djwong, hch, linux-fsdevel, linux-kernel, linux-xfs, patches,
willy
From: "Ritesh Harjani (IBM)" <ritesh.list@gmail.com>
[ 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 <willy@infradead.org>
Signed-off-by: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
Signed-off-by: Rajani Kantha <681739313@139.com>
---
fs/iomap/buffered-io.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/iomap/buffered-io.c b/fs/iomap/buffered-io.c
index 70e246f7e8fe..e4f58d1e12d4 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 */
--
2.34.1
^ permalink raw reply related [flat|nested] only message in thread
only message in thread, other threads:[~2026-01-23 6:33 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-01-23 6:33 [PATCH 6.1.y] iomap: Fix possible overflow condition in iomap_write_delalloc_scan Rajani Kantha
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox