diff options
| author |   Jaegeuk Kim <jaegeuk@kernel.org> | 2017-08-10 17:35:04 -0700 |
|---|---|---|
| committer |   Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2017-09-20 08:22:10 +0200 |
| commit | 96a069a6babb4a19eaaa6a7dd72943040f0a5848 (patch) | |
| tree | 0e66a51bd2030433d0a66aefb05a3cad01ce4d10 | |
| parent | sctp: fix missing wake ups in some situations (diff) | |
| download | linux-stable-96a069a6babb4a19eaaa6a7dd72943040f0a5848.tar.xz linux-stable-96a069a6babb4a19eaaa6a7dd72943040f0a5848.zip | |
f2fs: let fill_super handle roll-forward errors
commit afd2b4da40b3b567ef8d8e6881479345a2312a03 upstream.
If we set CP_ERROR_FLAG in roll-forward error, f2fs is no longer to proceed
any IOs due to f2fs_cp_error(). But, for example, if some stale data is involved
on roll-forward process, we're able to get -ENOENT, getting fs stuck.
If we get any error, let fill_super set SBI_NEED_FSCK and try to recover back
to stable point.
Reviewed-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
| -rw-r--r-- | fs/f2fs/recovery.c | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/fs/f2fs/recovery.c b/fs/f2fs/recovery.c index 907d6b7dde6a..14e88dbe671d 100644 --- a/fs/f2fs/recovery.c +++ b/fs/f2fs/recovery.c @@ -599,8 +599,6 @@ out: } clear_sbi_flag(sbi, SBI_POR_DOING); - if (err) - set_ckpt_flags(sbi, CP_ERROR_FLAG); mutex_unlock(&sbi->cp_mutex); /* let's drop all the directory inodes for clean checkpoint */ |