summaryrefslogtreecommitdiffstats
path: root/fs
diff options
context:
space:
mode:
authorChao Yu <chao2.yu@samsung.com>2015-07-17 18:05:21 +0800
committerJaegeuk Kim <jaegeuk@kernel.org>2015-08-05 08:08:12 -0700
commita5f64b6aa69b5cc05e198291811a2f3faf95b463 (patch)
treec529994d48adc21e3646871de638e249259993dc /fs
parent6a2905443cf27f9c14889428f14fccfb98ed97f4 (diff)
downloadlinux-a5f64b6aa69b5cc05e198291811a2f3faf95b463.tar.bz2
f2fs: fix to wait all atomic written pages writeback
This patch fixes the incorrect range (0, LONG_MAX) which is used in ranged fsync. If we use LONG_MAX as the parameter for indicating the end of file we want to synchronize, in 32-bits architecture machine, these datas after 4GB offset may not be persisted in storage after ->fsync returned. Here, we alter LONG_MAX to LLONG_MAX to fix this issue. Signed-off-by: Chao Yu <chao2.yu@samsung.com> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Diffstat (limited to 'fs')
-rw-r--r--fs/f2fs/file.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
index 15df014aadc7..d4da7fec757d 100644
--- a/fs/f2fs/file.c
+++ b/fs/f2fs/file.c
@@ -1357,7 +1357,7 @@ static int f2fs_ioc_commit_atomic_write(struct file *filp)
commit_inmem_pages(inode, false);
}
- ret = f2fs_sync_file(filp, 0, LONG_MAX, 0);
+ ret = f2fs_sync_file(filp, 0, LLONG_MAX, 0);
mnt_drop_write_file(filp);
return ret;
}