f2fs: drop FI_UPDATE_WRITE tag after f2fs_issue_flush

If we failed to issue flush in ->fsync, we need to keep FI_UPDATE_WRITE
flag to make sure triggering flush in next ->fsync.

Signed-off-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>

diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
index 517e112c8a9a943467492435c9f15c1668e079a8..78fff137a914131592fec2e0f000d64a45821ab7 100644 (file)
--- a/fs/f2fs/file.c
+++ b/fs/f2fs/file.c
@@ -294,10 +294,12 @@ sync_nodes:
        remove_ino_entry(sbi, ino, APPEND_INO);
        clear_inode_flag(inode, FI_APPEND_WRITE);
 flush_out:
-       remove_ino_entry(sbi, ino, UPDATE_INO);
-       clear_inode_flag(inode, FI_UPDATE_WRITE);
        if (!atomic)
                ret = f2fs_issue_flush(sbi);
+       if (!ret) {
+               remove_ino_entry(sbi, ino, UPDATE_INO);
+               clear_inode_flag(inode, FI_UPDATE_WRITE);
+       }
        f2fs_update_time(sbi, REQ_TIME);
 out:
        trace_f2fs_sync_file_exit(inode, need_cp, datasync, ret);