gfs2: don't worry about I_DIRTY_TIME in gfs2_fsync()
authorEric Biggers <ebiggers@google.com>
Tue, 12 Jan 2021 19:02:52 +0000 (11:02 -0800)
committerJan Kara <jack@suse.cz>
Wed, 13 Jan 2021 16:26:53 +0000 (17:26 +0100)
commit3aac630b5ce18b0a7e34cb35cdd99fcc508edc92
treec4da3550d112b52c211a5b8c8583c2af5dda6277
parentda0c4c60d8c7c8cc5266b0c5fe7bdf136e5e6415
gfs2: don't worry about I_DIRTY_TIME in gfs2_fsync()

The I_DIRTY_TIME flag is primary used within the VFS, and there's no
reason for ->fsync() implementations to do anything with it.  This is
because when !datasync, the VFS will expire dirty timestamps before
calling ->fsync().  (See vfs_fsync_range().)  This turns I_DIRTY_TIME
into I_DIRTY_SYNC.

Therefore, change gfs2_fsync() to not check for I_DIRTY_TIME.

Link: https://lore.kernel.org/r/20210112190253.64307-11-ebiggers@kernel.org
Reviewed-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Jan Kara <jack@suse.cz>
Signed-off-by: Eric Biggers <ebiggers@google.com>
Signed-off-by: Jan Kara <jack@suse.cz>
fs/gfs2/file.c