Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit ed6712dc authored by Chao Yu's avatar Chao Yu Committed by Jaegeuk Kim
Browse files

f2fs: fix extent corrupotion during directIO in LFS mode 



In LFS mode, por_fsstress testcase reports a bug as below:

[ASSERT] (fsck_chk_inode_blk: 931)  --> ino: 0x12fe has wrong ext: [pgofs:142, blk:215424, len:16]

Since commit f847c699cff3 ("f2fs: allow out-place-update for direct
IO in LFS mode"), we start to allow OPU mode for direct IO, however,
we missed to update extent cache in __allocate_data_block(), finally,
it cause extent field being inconsistent with physical block address,
fix it.

Fixes: f847c699cff3 ("f2fs: allow out-place-update for direct IO in LFS mode")
Signed-off-by: default avatarChao Yu <yuchao0@huawei.com>
Signed-off-by: default avatarJaegeuk Kim <jaegeuk@kernel.org>
parent 693b3bae

fs/f2fs/data.c

+1 −1
Original line number Diff line number Diff line
@@ -1053,7 +1053,7 @@ static int __allocate_data_block(struct dnode_of_data *dn, int seg_type) 
	if (GET_SEGNO(sbi, old_blkaddr) != NULL_SEGNO)

		invalidate_mapping_pages(META_MAPPING(sbi),

					old_blkaddr, old_blkaddr);

	f2fs_set_data_blkaddr(dn);

	f2fs_update_data_blkaddr(dn, dn->data_blkaddr);



	/*

	 * i_size will be updated by direct_IO. Otherwise, we'll get stale