summaryrefslogtreecommitdiffstats
path: root/fs/ext4/extents_status.c
diff options
context:
space:
mode:
authorZheng Liu2013-03-11 02:08:52 +0100
committerTheodore Ts'o2013-03-11 02:08:52 +0100
commitcdee78433c138c2f2018a6884673739af2634787 (patch)
tree91ac86ddb480e0df9385917999645a8c0d35c68b /fs/ext4/extents_status.c
parentext4: add self-testing infrastructure to do a sanity check (diff)
downloadkernel-qcow2-linux-cdee78433c138c2f2018a6884673739af2634787.tar.gz
kernel-qcow2-linux-cdee78433c138c2f2018a6884673739af2634787.tar.xz
kernel-qcow2-linux-cdee78433c138c2f2018a6884673739af2634787.zip
ext4: fix wrong m_len value after unwritten extent conversion
The ext4_ext_handle_uninitialized_extents() function was assuming the return value of ext4_ext_map_blocks() is equal to map->m_len. This incorrect assumption was harmless until we started use status tree as a extent cache because we need to update status tree according to 'm_len' value. Meanwhile this commit marks EXT4_MAP_MAPPED flag after unwritten extent conversion. It shouldn't cause a bug because we update status tree according to checking EXT4_MAP_UNWRITTEN flag. But it should be fixed. After applied this commit, the following error message from self-testing infrastructure disappears. ... kernel: ES len assertation failed for inode: 230 retval 1 != map->m_len 3 in ext4_map_blocks (allocation) ... Signed-off-by: Zheng Liu <wenqing.lz@taobao.com> Signed-off-by: "Theodore Ts'o" <tytso@mit.edu> Cc: Dmitry Monakhov <dmonakhov@openvz.org>
Diffstat (limited to 'fs/ext4/extents_status.c')
0 files changed, 0 insertions, 0 deletions