The patch titled
Subject: omfs: fix potential integer overflow in allocator
has been removed from the -mm tree. Its filename was
omfs-fix-potential-integer-overflow-in-allocator.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
From: Bob Copeland <me@xxxxxxxxxxxxxxx>
Subject: omfs: fix potential integer overflow in allocator
Both 'i' and 'bits_per_entry' are signed integers but the result is a u64
block number. Cast i to u64 to avoid truncation on 32-bit targets.
Found by Coverity (CID 200679).
Signed-off-by: Bob Copeland <me@xxxxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
fs/omfs/bitmap.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN fs/omfs/bitmap.c~omfs-fix-potential-integer-overflow-in-allocator fs/omfs/bitmap.c
--- a/fs/omfs/bitmap.c~omfs-fix-potential-integer-overflow-in-allocator
+++ a/fs/omfs/bitmap.c
@@ -159,7 +159,7 @@ int omfs_allocate_range(struct super_blo
goto out;
found:
- *return_block = i * bits_per_entry + bit;
+ *return_block = (u64) i * bits_per_entry + bit;
*return_size = run;
ret = set_run(sb, i, bits_per_entry, bit, run, 1);
_
Patches currently in -mm which might be from me@xxxxxxxxxxxxxxx are
linux-next.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
