diff options
author | Chao Yu <chao2.yu@samsung.com> | 2015-07-17 10:05:21 (GMT) |
---|---|---|
committer | Jaegeuk Kim <jaegeuk@kernel.org> | 2015-08-05 15:08:12 (GMT) |
commit | a5f64b6aa69b5cc05e198291811a2f3faf95b463 (patch) | |
tree | c529994d48adc21e3646871de638e249259993dc | |
parent | 6a2905443cf27f9c14889428f14fccfb98ed97f4 (diff) | |
download | linux-a5f64b6aa69b5cc05e198291811a2f3faf95b463.tar.xz |
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>
-rw-r--r-- | fs/f2fs/file.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c index 15df014..d4da7fe 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; } |