f2fs: don't bother with inode->i_version

f2fs does not set the SB_I_VERSION flag, so the i_version will never
be incremented on write. It was recently changed to increment the
i_version on a quota write, which isn't necessary here.

Signed-off-by: Jeff Layton <jlayton@redhat.com>
Reviewed-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>

diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c
index 91eaa7b235eb18cac1a8016a46240fba0bbf318f..031cb26a3a7671ac93aa248ce1a546fe898d2ea9 100644 (file)
--- a/fs/f2fs/super.c
+++ b/fs/f2fs/super.c
@@ -664,7 +664,6 @@ static struct inode *f2fs_alloc_inode(struct super_block *sb)
        init_once((void *) fi);
 
        /* Initialize f2fs-specific inode info */
-       fi->vfs_inode.i_version = 1;
        atomic_set(&fi->dirty_pages, 0);
        fi->i_current_depth = 1;
        fi->i_advise = 0;
@@ -1460,7 +1459,6 @@ retry:
 
        if (len == towrite)
                return err;
-       inode->i_version++;
        inode->i_mtime = inode->i_ctime = current_time(inode);
        f2fs_mark_inode_dirty_sync(inode, false);
        return len - towrite;