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:
@@ -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(
|
||||
|
Reference in New Issue
Block a user