nilfs2-fix-possible-int-overflows-in-nilfs_fiemap.patch removed from -mm tree
The quilt patch titled
Subject: nilfs2: fix possible int overflows in nilfs_fiemap()
has been removed from the -mm tree. Its filename was
nilfs2-fix-possible-int-overflows-in-nilfs_fiemap.patch
This patch was dropped because it was merged into the mm-hotfixes-stable branch of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: Nikita Zhandarovich <[email protected]>
Subject: nilfs2: fix possible int overflows in nilfs_fiemap()
Date: Sat, 25 Jan 2025 07:20:53 +0900
Since nilfs_bmap_lookup_contig() in nilfs_fiemap() calculates its result by being prepared to go through potentially maxblocks == INT_MAX blocks, the value in n may experience an overflow caused by left shift of blkbits.
While it is extremely unlikely to occur, play it safe and cast right hand expression to wider type to mitigate the issue.
Found by Linux Verification Center (linuxtesting.org) with static analysis tool SVACE.
---
fs/nilfs2/inode.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
fs/nilfs2/inode.c renamed from fs/nilfs2/inode.c~nilfs2-fix-possible-int-overflows-in-nilfs_fiemap +3 -3
@@ -1186,7 +1186,7 @@ int nilfs_fiemap(struct inode *inode, stif (size) {if (phys && blkphy << blkbits == phys + size) {/* The current extent goes on */ - size += n << blkbits; + size += (u64 )n << blkbits; }else {/* Terminate the current extent */ ret = fiemap_fill_next_extent(
@@ -1199,14 +1199,14 @@ int nilfs_fiemap(struct inode *inode, st flags =FIEMAP_EXTENT_MERGED ; logical = blkoff << blkbits; phys = blkphy << blkbits; - size = n << blkbits; + size = (u64 )n << blkbits; } }else {/* Start a new extent */ flags =FIEMAP_EXTENT_MERGED ; logical = blkoff << blkbits; phys = blkphy << blkbits; - size = n << blkbits; + size = (u64 )n << blkbits; } blkoff += n; }
_
Patches currently in -mm which might be from [email protected] are