diff options
author | Jaegeuk Kim <jaegeuk.kim@samsung.com> | 2013-07-03 10:55:52 +0900 |
---|---|---|
committer | Marek Szyprowski <m.szyprowski@samsung.com> | 2014-05-15 07:21:32 +0200 |
commit | 6d6fb851782ba9a0ca796639bf41afca99a4a608 (patch) | |
tree | 1b7d90063681f7fe57b9455034a0f2c9afde1d39 /fs | |
parent | ab3fcd68c781f859f2cd734681445e0af63c2bb4 (diff) | |
download | linux-3.10-6d6fb851782ba9a0ca796639bf41afca99a4a608.tar.gz linux-3.10-6d6fb851782ba9a0ca796639bf41afca99a4a608.tar.bz2 linux-3.10-6d6fb851782ba9a0ca796639bf41afca99a4a608.zip |
f2fs: recover date requested by fdatasync
In order to support SQLite that uses fdatasync instead of fsync, we should
guarantee the data requested by fdatasync can be recovered after sudden-power-
off.
So, let's remove the fdatasync condition in f2fs_sync_file.
Otherwise, we can restore the data after sudden-power-off due to nonexistence
of any fsync mark'ed node blocks.
Signed-off-by: Jaegeuk Kim <jaegeuk.kim@samsung.com>
Diffstat (limited to 'fs')
-rw-r--r-- | fs/f2fs/file.c | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c index d2d2b7dbdcc..157a6357f14 100644 --- a/fs/f2fs/file.c +++ b/fs/f2fs/file.c @@ -147,9 +147,10 @@ int f2fs_sync_file(struct file *file, loff_t start, loff_t end, int datasync) mutex_lock(&inode->i_mutex); - if (datasync && !(inode->i_state & I_DIRTY_DATASYNC)) - goto out; - + /* + * Both of fdatasync() and fsync() are able to be recovered from + * sudden-power-off. + */ if (!S_ISREG(inode->i_mode) || inode->i_nlink != 1) need_cp = true; else if (file_wrong_pino(inode)) |