diff options
author | Chao Yu <yuchao0@huawei.com> | 2019-08-28 17:33:35 +0800 |
---|---|---|
committer | Jaegeuk Kim <jaegeuk@kernel.org> | 2019-09-16 08:38:49 -0700 |
commit | 86f35dc39ef9cdc5d33548e2d4ddac815a39e542 (patch) | |
tree | 24e7dbcb9e33c0ac5dee58f68b1e3c1f109758a4 /fs/autofs | |
parent | 1166c1f2f69117ad254189ca781287afa6e550b6 (diff) | |
download | linux-86f35dc39ef9cdc5d33548e2d4ddac815a39e542.tar.gz |
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: Chao Yu <yuchao0@huawei.com> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Diffstat (limited to 'fs/autofs')
0 files changed, 0 insertions, 0 deletions