ext4: clear i_data in ext4_inode_info when removing inline data

Message ID 20180615043408.26275-1-tytso@mit.edu
State New
Headers show
  • ext4: clear i_data in ext4_inode_info when removing inline data
Related show

Commit Message

Theodore Y. Ts'o June 15, 2018, 4:34 a.m.
When converting from an inode from storing the data in-line to a data
block, ext4_destroy_inline_data_nolock() was only clearing the on-disk
copy of the i_blocks[] array.  It was not clearing copy of the
i_blocks[] in ext4_inode_info, in i_data[], which is the copy actually
used by ext4_map_blocks().

This didn't matter much if we are using extents, since the extents
header would be invalid and thus the extents could would re-initialize
the extents tree.  But if we are using indirect blocks, the previous
contents of the i_blocks array will be treated as block numbers, with
potentially catastrophic results to the file system integrity and/or
user data.

This gets worse if the file system is using a 1k block size and
s_first_data is zero, but even without this, the file system can get
quite badly corrupted.


Signed-off-by: Theodore Ts'o <tytso@mit.edu>
 fs/ext4/inline.c | 1 +
 1 file changed, 1 insertion(+)


diff --git a/fs/ext4/inline.c b/fs/ext4/inline.c
index 44b4fcdc3755..d79115d8d716 100644
--- a/fs/ext4/inline.c
+++ b/fs/ext4/inline.c
@@ -437,6 +437,7 @@  static int ext4_destroy_inline_data_nolock(handle_t *handle,
 	memset((void *)ext4_raw_inode(&is.iloc)->i_block,
+	memset(ei->i_data, 0, EXT4_MIN_INLINE_DATA_SIZE);
 	if (ext4_has_feature_extents(inode->i_sb)) {
 		if (S_ISDIR(inode->i_mode) ||