Messages in this thread Patch in this message | | | From | Mike Hommey <> | Subject | [PATCH] Fix generic_block_fiemap for files bigger than 4GB | Date | Mon, 26 Oct 2009 18:24:28 +0100 |
| |
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@glandium.org> --- fs/ioctl.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/fs/ioctl.c b/fs/ioctl.c index 7b17a14..6c75110 100644 --- a/fs/ioctl.c +++ b/fs/ioctl.c @@ -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; -- 1.6.5
| |