Btrfs: init inode ordered_data_close flag properly
This flag is used to decide when we need to send a given file through the ordered code to make sure it is fully written before a transaction commits. It was not being properly set to zero when the inode was being setup. Signed-off-by: Chris Mason <chris.mason@oracle.com>
This commit is contained in:
parent
46a53cca82
commit
2757495c90
|
@ -3122,6 +3122,7 @@ static noinline void init_btrfs_i(struct inode *inode)
|
||||||
bi->flags = 0;
|
bi->flags = 0;
|
||||||
bi->index_cnt = (u64)-1;
|
bi->index_cnt = (u64)-1;
|
||||||
bi->last_unlink_trans = 0;
|
bi->last_unlink_trans = 0;
|
||||||
|
bi->ordered_data_close = 0;
|
||||||
extent_map_tree_init(&BTRFS_I(inode)->extent_tree, GFP_NOFS);
|
extent_map_tree_init(&BTRFS_I(inode)->extent_tree, GFP_NOFS);
|
||||||
extent_io_tree_init(&BTRFS_I(inode)->io_tree,
|
extent_io_tree_init(&BTRFS_I(inode)->io_tree,
|
||||||
inode->i_mapping, GFP_NOFS);
|
inode->i_mapping, GFP_NOFS);
|
||||||
|
|
Loading…
Reference in New Issue