summaryrefslogtreecommitdiff
path: root/fs/f2fs/file.c
diff options
context:
space:
mode:
authorQilong Zhang <zhangqilong3@huawei.com>2020-06-28 19:23:03 +0800
committerJaegeuk Kim <jaegeuk@kernel.org>2020-07-07 21:51:44 -0700
commit97767500781fae9c53b7d227f99f1dbb0dfe9a4f (patch)
tree7a54ad231d4924dacf5058b69d3ca7342fb874ef /fs/f2fs/file.c
parentf608c38c59c6020bfde14af88630b8d7817003f9 (diff)
f2fs: add f2fs_gc exception handle in f2fs_ioc_gc_range
When f2fs_ioc_gc_range performs multiple segments gc ops, the return value of f2fs_ioc_gc_range is determined by the last segment gc ops. If its ops failed, the f2fs_ioc_gc_range will be considered to be failed despite some of previous segments gc ops succeeded. Therefore, so we fix: Redefine the return value of getting victim ops and add exception handle for f2fs_gc. In particular, 1).if target has no valid block, it will go on. 2).if target sectoion has valid block(s), but it is current section, we will reminder the caller. Signed-off-by: Qilong Zhang <zhangqilong3@huawei.com> Reviewed-by: Chao Yu <yuchao0@huawei.com> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Diffstat (limited to 'fs/f2fs/file.c')
-rw-r--r--fs/f2fs/file.c5
1 files changed, 5 insertions, 0 deletions
diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
index e15d4ce4c08e..6ef2656c6171 100644
--- a/fs/f2fs/file.c
+++ b/fs/f2fs/file.c
@@ -2525,6 +2525,11 @@ do_more:
}
ret = f2fs_gc(sbi, range.sync, true, GET_SEGNO(sbi, range.start));
+ if (ret) {
+ if (ret == -EBUSY)
+ ret = -EAGAIN;
+ goto out;
+ }
range.start += BLKS_PER_SEC(sbi);
if (range.start <= end)
goto do_more;