f2fs: Fix mount failure due to SPO after a successful online resize FS
authorSahitya Tummala <stummala@codeaurora.org>
Tue, 3 Mar 2020 14:29:25 +0000 (19:59 +0530)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Thu, 23 Apr 2020 08:36:33 +0000 (10:36 +0200)
commit066f1e4174f2adbee9aaf19e7e236289e68ce756
tree1c25bb39dbaac5eae1ea7acfb2fb22b99b6a9894
parentea468f37370a92c64656b3a7b51406cfab212188
f2fs: Fix mount failure due to SPO after a successful online resize FS

[ Upstream commit 682756827501dc52593bf490f2d437c65ec9efcb ]

Even though online resize is successfully done, a SPO immediately
after resize, still causes below error in the next mount.

[   11.294650] F2FS-fs (sda8): Wrong user_block_count: 2233856
[   11.300272] F2FS-fs (sda8): Failed to get valid F2FS checkpoint

This is because after FS metadata is updated in update_fs_metadata()
if the SBI_IS_DIRTY is not dirty, then CP will not be done to reflect
the new user_block_count.

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/gc.c