summaryrefslogtreecommitdiffstats
path: root/fs/f2fs/segment.c
diff options
context:
space:
mode:
authorJaegeuk Kim <jaegeuk@kernel.org>2014-10-27 11:04:35 -0700
committerJaegeuk Kim <jaegeuk@kernel.org>2014-11-03 16:07:37 -0800
commitca4b02eeed752c02da0df9da6f9d3c978f9fa9e1 (patch)
tree86e0e84c0d8719234059cdf0ec94cd105489baeb /fs/f2fs/segment.c
parent9234f3190bf8b25b11b105191d408ac50a107948 (diff)
downloadlinux-ca4b02eeed752c02da0df9da6f9d3c978f9fa9e1.tar.bz2
f2fs: call write_checkpoint under disabled gc
During the write_checkpoint, we should avoid f2fs_gc trigger to avoid any filesystem consistency. Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Diffstat (limited to 'fs/f2fs/segment.c')
-rw-r--r--fs/f2fs/segment.c2
1 files changed, 2 insertions, 0 deletions
diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
index 21ccc4816474..d391a5913c79 100644
--- a/fs/f2fs/segment.c
+++ b/fs/f2fs/segment.c
@@ -1046,7 +1046,9 @@ int f2fs_trim_fs(struct f2fs_sb_info *sbi, struct fstrim_range *range)
cpc.trim_minlen = range->minlen >> sbi->log_blocksize;
/* do checkpoint to issue discard commands safely */
+ mutex_lock(&sbi->gc_mutex);
write_checkpoint(sbi, &cpc);
+ mutex_unlock(&sbi->gc_mutex);
out:
range->len = cpc.trimmed << sbi->log_blocksize;
return 0;