mirror of
https://github.com/followmsi/android_kernel_google_msm.git
synced 2024-11-06 23:17:41 +00:00
Btrfs: zero unused bytes in inode item
The otime field is not zeroed, so users will see random otime in an old filesystem with a new kernel which has otime support in the future. The reserved bytes are also not zeroed, and we'll have compatibility issue if we make use of those bytes. Signed-off-by: Li Zefan <lizefan@huawei.com>
This commit is contained in:
parent
b4d7c3c945
commit
293f7e0740
2 changed files with 3 additions and 0 deletions
|
@ -62,6 +62,7 @@ static inline void btrfs_init_delayed_node(
|
|||
INIT_LIST_HEAD(&delayed_node->n_list);
|
||||
INIT_LIST_HEAD(&delayed_node->p_list);
|
||||
delayed_node->bytes_reserved = 0;
|
||||
memset(&delayed_node->inode_item, 0, sizeof(delayed_node->inode_item));
|
||||
}
|
||||
|
||||
static inline int btrfs_is_continuous_delayed_item(
|
||||
|
|
|
@ -4693,6 +4693,8 @@ static struct inode *btrfs_new_inode(struct btrfs_trans_handle *trans,
|
|||
inode->i_mtime = inode->i_atime = inode->i_ctime = CURRENT_TIME;
|
||||
inode_item = btrfs_item_ptr(path->nodes[0], path->slots[0],
|
||||
struct btrfs_inode_item);
|
||||
memset_extent_buffer(path->nodes[0], 0, (unsigned long)inode_item,
|
||||
sizeof(*inode_item));
|
||||
fill_inode_item(trans, path->nodes[0], inode_item, inode);
|
||||
|
||||
ref = btrfs_item_ptr(path->nodes[0], path->slots[0] + 1,
|
||||
|
|
Loading…
Reference in a new issue