f2fs: Add a new CP flag to help fsck fix resize SPO issues
authorSahitya Tummala <stummala@codeaurora.org>
Tue, 3 Mar 2020 14:29:26 +0000 (19:59 +0530)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Thu, 23 Apr 2020 08:36:33 +0000 (10:36 +0200)
commit380d1290460345bc69aadd3d4ca9e73b62f29cb8
tree45c2fe224f498eac59a845625fe8d8c64ac6e660
parent066f1e4174f2adbee9aaf19e7e236289e68ce756
f2fs: Add a new CP flag to help fsck fix resize SPO issues

[ Upstream commit c84ef3c5e65ccf99a7a91a4d731ebb5d6331a178 ]

Add and set a new CP flag CP_RESIZEFS_FLAG during
online resize FS to help fsck fix the metadata mismatch
that may happen due to SPO during resize, where SB
got updated but CP data couldn't be written yet.

fsck errors -
Info: CKPT version = 6ed7bccb
        Wrong user_block_count(2233856)
[f2fs_do_mount:3365] Checkpoint is polluted

Signed-off-by: Sahitya Tummala <stummala@codeaurora.org>
Reviewed-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
fs/f2fs/checkpoint.c
include/linux/f2fs_fs.h