The patch titled
__generic_block_fiemap(): fix for files bigger than 4GB
has been removed from the -mm tree. Its filename was
__generic_block_fiemap-fix-for-files-bigger-than-4gb.patch
This patch was dropped because it was merged into mainline or a subsystem tree
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: __generic_block_fiemap(): fix for files bigger than 4GB
From: Mike Hommey <mh@xxxxxxxxxxxx>
Because of an integer overflow on start_blk, various kind of wrong results
would be returned by the generic_block_fiemap() handler, such as no
extents when there is a 4GB+ hole at the beginning of the file, or wrong
fe_logical when an extent starts after the first 4GB.
Signed-off-by: Mike Hommey <mh@xxxxxxxxxxxx>
Cc: Alexander Viro <viro@xxxxxxxxxxxxxxxxxx>
Cc: Steven Whitehouse <swhiteho@xxxxxxxxxx>
Cc: Theodore Ts'o <tytso@xxxxxxx>
Cc: Eric Sandeen <sandeen@xxxxxxx>
Cc: Josef Bacik <jbacik@xxxxxxxxxx>
Cc: Mark Fasheh <mfasheh@xxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
diff -puN fs/ioctl.c~__generic_block_fiemap-fix-for-files-bigger-than-4gb fs/ioctl.c
--- a/fs/ioctl.c~__generic_block_fiemap-fix-for-files-bigger-than-4gb
+++ a/fs/ioctl.c
@@ -254,7 +254,7 @@ int __generic_block_fiemap(struct inode
u64 len, get_block_t *get_block)
{
struct buffer_head tmp;
- unsigned int start_blk;
+ unsigned long long start_blk;
long long length = 0, map_len = 0;
u64 logical = 0, phys = 0, size = 0;
u32 flags = FIEMAP_EXTENT_MERGED;
_
Patches currently in -mm which might be from mh@xxxxxxxxxxxx are
--
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
