diff options
| author | Eric Biggers <[email protected]> | 2021-01-12 11:02:52 -0800 |
|---|---|---|
| committer | Jan Kara <[email protected]> | 2021-01-13 17:26:53 +0100 |
| commit | 3aac630b5ce18b0a7e34cb35cdd99fcc508edc92 (patch) | |
| tree | c4da3550d112b52c211a5b8c8583c2af5dda6277 /tools/perf/scripts/python/Perf-Trace-Util/lib/Perf/Trace/EventClass.py | |
| parent | da0c4c60d8c7c8cc5266b0c5fe7bdf136e5e6415 (diff) | |
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/[email protected]
Reviewed-by: Christoph Hellwig <[email protected]>
Reviewed-by: Jan Kara <[email protected]>
Signed-off-by: Eric Biggers <[email protected]>
Signed-off-by: Jan Kara <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/Perf-Trace-Util/lib/Perf/Trace/EventClass.py')
0 files changed, 0 insertions, 0 deletions