diff options
author | Chao Yu <chao2.yu@samsung.com> | 2015-08-19 14:11:19 +0300 |
---|---|---|
committer | Jaegeuk Kim <jaegeuk@kernel.org> | 2015-08-22 08:45:14 +0300 |
commit | e2b4e2bc8865e03eecd49caa9713a2402a96bba9 (patch) | |
tree | a1c1c7e2effcb9816fa7151ebe4d1cc1533616d5 /lib/decompress_unxz.c | |
parent | c031f6a904975d5fa84c541333cce444a21ca713 (diff) | |
download | linux-e2b4e2bc8865e03eecd49caa9713a2402a96bba9.tar.xz |
f2fs: fix incorrect mapping for bmap
The test step is like below:
1. touch file
2. truncate -s $((1024*1024)) file
3. fallocate -o 0 -l $((1024*1024)) file
4. fibmap.f2fs file
Our result of fibmap.f2fs showed below is not correct:
file_pos start_blk end_blk blks
0 -937166132 -937166132 1
4096 -937166132 -937166132 1
8192 -937166132 -937166132 1
12288 -937166132 -937166132 1
16384 -937166132 -937166132 1
20480 -937166132 -937166132 1
...
1040384 -937166132 -937166132 1
1044480 -937166132 -937166132 1
This is because f2fs_map_blocks will return with no error when meeting
a hole or preallocated block, the caller __get_data_block will map the
uninitialized variable value to bh->b_blocknr.
Unfortunately generic_block_bmap will neither check the return value of
get_data() nor check mapping info of buffer_head, result in returning
the random block address.
After fixing the issue, our result shows correctly:
file_pos start_blk end_blk blks
0 0 0 256
Signed-off-by: Chao Yu <chao2.yu@samsung.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Diffstat (limited to 'lib/decompress_unxz.c')
0 files changed, 0 insertions, 0 deletions