Commit 86f35dc3 authored Aug 28, 2019 by Chao Yu Committed by Jaegeuk Kim Sep 16, 2019

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 f847c699 ("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: f847c699 ("f2fs: allow out-place-update for direct IO in LFS mode")
Signed-off-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>

parent 1166c1f2

fs/f2fs/data.c

+1 −1

Original line number	Diff line number	Diff line
		@@ -1018,7 +1018,7 @@ alloc:
		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

Admin message