diff options
| author | Linus Torvalds <torvalds@linux-foundation.org> | 2021-02-22 22:17:39 +0100 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2021-02-22 22:17:39 +0100 |
| commit | d61c6a58ae30e80fb68925877cab06ad7a4ce41e (patch) | |
| tree | ed7bc90b257b042c6b5ca4b908820af52b4bd1d5 /Documentation/filesystems | |
| parent | Merge tag 'exfat-for-5.12-rc1' of git://git.kernel.org/pub/scm/linux/kernel/g... (diff) | |
| parent | ext4: simplify i_state checks in __ext4_update_other_inode_time() (diff) | |
| download | linux-d61c6a58ae30e80fb68925877cab06ad7a4ce41e.tar.xz linux-d61c6a58ae30e80fb68925877cab06ad7a4ce41e.zip | |
Merge tag 'lazytime_for_v5.12-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs
Pull lazytime updates from Jan Kara:
"Cleanups of the lazytime handling in the writeback code making rules
for calling ->dirty_inode() filesystem handlers saner"
* tag 'lazytime_for_v5.12-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs:
ext4: simplify i_state checks in __ext4_update_other_inode_time()
gfs2: don't worry about I_DIRTY_TIME in gfs2_fsync()
fs: improve comments for writeback_single_inode()
fs: drop redundant check from __writeback_single_inode()
fs: clean up __mark_inode_dirty() a bit
fs: pass only I_DIRTY_INODE flags to ->dirty_inode
fs: don't call ->dirty_inode for lazytime timestamp updates
fat: only specify I_DIRTY_TIME when needed in fat_update_time()
fs: only specify I_DIRTY_TIME when needed in generic_update_time()
fs: correctly document the inode dirty flags
Diffstat (limited to 'Documentation/filesystems')
| -rw-r--r-- | Documentation/filesystems/vfs.rst | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/Documentation/filesystems/vfs.rst b/Documentation/filesystems/vfs.rst index 18d69a4559d6..a4d64b1b4295 100644 --- a/Documentation/filesystems/vfs.rst +++ b/Documentation/filesystems/vfs.rst @@ -270,7 +270,10 @@ or bottom half). ->alloc_inode. ``dirty_inode`` - this method is called by the VFS to mark an inode dirty. + this method is called by the VFS when an inode is marked dirty. + This is specifically for the inode itself being marked dirty, + not its data. If the update needs to be persisted by fdatasync(), + then I_DIRTY_DATASYNC will be set in the flags argument. ``write_inode`` this method is called when the VFS needs to write an inode to |