summaryrefslogtreecommitdiffstats
path: root/fs
diff options
context:
space:
mode:
authorJaegeuk Kim <jaegeuk@kernel.org>2017-08-10 17:35:04 -0700
committerJaegeuk Kim <jaegeuk@kernel.org>2017-08-21 15:55:03 -0700
commitafd2b4da40b3b567ef8d8e6881479345a2312a03 (patch)
tree5cf197ca20a743c2670447a63b7197418c463eac /fs
parentf2220c7f155c99392b307be3012aae976a503afe (diff)
downloadop-kernel-dev-afd2b4da40b3b567ef8d8e6881479345a2312a03.zip
op-kernel-dev-afd2b4da40b3b567ef8d8e6881479345a2312a03.tar.gz
f2fs: let fill_super handle roll-forward errors
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. Cc: <stable@vger.kernel.org> Reviewed-by: Chao Yu <yuchao0@huawei.com> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Diffstat (limited to 'fs')
-rw-r--r--fs/f2fs/recovery.c2
1 files changed, 0 insertions, 2 deletions
diff --git a/fs/f2fs/recovery.c b/fs/f2fs/recovery.c
index a3d0261..f707d81 100644
--- a/fs/f2fs/recovery.c
+++ b/fs/f2fs/recovery.c
@@ -649,8 +649,6 @@ skip:
}
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 */
OpenPOWER on IntegriCloud