f2fs: update i_size when __allocate_data_block
The f2fs_direct_IO uses __allocate_data_block, but inside the allocation path, we should update i_size at the changed time to update its inode page. Otherwise, we can get wrong i_size after roll-forward recovery. Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
This commit is contained in:
parent
90a893c749
commit
976e4c50ae
|
@ -572,9 +572,11 @@ struct page *get_new_data_page(struct inode *inode,
|
||||||
static int __allocate_data_block(struct dnode_of_data *dn)
|
static int __allocate_data_block(struct dnode_of_data *dn)
|
||||||
{
|
{
|
||||||
struct f2fs_sb_info *sbi = F2FS_I_SB(dn->inode);
|
struct f2fs_sb_info *sbi = F2FS_I_SB(dn->inode);
|
||||||
|
struct f2fs_inode_info *fi = F2FS_I(dn->inode);
|
||||||
struct f2fs_summary sum;
|
struct f2fs_summary sum;
|
||||||
block_t new_blkaddr;
|
block_t new_blkaddr;
|
||||||
struct node_info ni;
|
struct node_info ni;
|
||||||
|
pgoff_t fofs;
|
||||||
int type;
|
int type;
|
||||||
|
|
||||||
if (unlikely(is_inode_flag_set(F2FS_I(dn->inode), FI_NO_ALLOC)))
|
if (unlikely(is_inode_flag_set(F2FS_I(dn->inode), FI_NO_ALLOC)))
|
||||||
|
@ -597,6 +599,12 @@ static int __allocate_data_block(struct dnode_of_data *dn)
|
||||||
update_extent_cache(new_blkaddr, dn);
|
update_extent_cache(new_blkaddr, dn);
|
||||||
clear_inode_flag(F2FS_I(dn->inode), FI_NO_EXTENT);
|
clear_inode_flag(F2FS_I(dn->inode), FI_NO_EXTENT);
|
||||||
|
|
||||||
|
/* update i_size */
|
||||||
|
fofs = start_bidx_of_node(ofs_of_node(dn->node_page), fi) +
|
||||||
|
dn->ofs_in_node;
|
||||||
|
if (i_size_read(dn->inode) < ((fofs + 1) << PAGE_CACHE_SHIFT))
|
||||||
|
i_size_write(dn->inode, ((fofs + 1) << PAGE_CACHE_SHIFT));
|
||||||
|
|
||||||
dn->data_blkaddr = new_blkaddr;
|
dn->data_blkaddr = new_blkaddr;
|
||||||
return 0;
|
return 0;
|
||||||
}
|
}
|
||||||
|
|
Loading…
Reference in New Issue