__generic_block_fiemap(): fix for files bigger than 4GB

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 <[email protected]>
Cc: Alexander Viro <[email protected]>
Cc: Steven Whitehouse <[email protected]>
Cc: Theodore Ts'o <[email protected]>
Cc: Eric Sandeen <[email protected]>
Cc: Josef Bacik <[email protected]>
Cc: Mark Fasheh <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
This commit is contained in:
Mike Hommey 2009-11-11 14:26:55 -08:00 • committed by Linus Torvalds
commit e04b5ef8b4

View file

@ -254,7 +254,7 @@ int __generic_block_fiemap(struct inode *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;