diff options
| author | Jaegeuk Kim <jaegeuk@kernel.org> | 2017-08-11 03:35:04 +0300 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2017-09-20 09:27:47 +0300 |
| commit | be009dd06669d6df7c038e0566f8ce0901460e24 (patch) | |
| tree | 3a81007df47ffcfaa92de1893e77435188390b9e | |
| parent | ffe6e0e9c2bf12c316d71d661621ff602b3a162e (diff) | |
| download | linux-be009dd06669d6df7c038e0566f8ce0901460e24.tar.xz | |
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 */ |