On Thu, Mar 26, 2020 at 02:22:12PM +1100, Dave Chinner wrote: > On Wed, Mar 25, 2020 at 01:28:23PM +0100, Christoph Hellwig wrote: > > In the case that an inode has dirty timestamp for longer than the > > lazytime expiration timeout (or if all such inodes are being flushed > > out due to a sync or syncfs system call), we need to inform the file > > system that the inode is dirty so that the inode's timestamps can be > > copied out to the on-disk data structures. That's because if the file > > system supports lazytime, it will have ignored the dirty_inode(inode, > > I_DIRTY_TIME) notification when the timestamp was modified in memory.q > > Previously, this was accomplished by calling mark_inode_dirty_sync(), > > but that has the unfortunate side effect of also putting the inode the > > writeback list, and that's not necessary in this case, since we will > > immediately call write_inode() afterwards. Replace the call to > > mark_inode_dirty_sync() with a new lazytime_expired method to clearly > > separate out this case. > > > hmmm. Doesn't this cause issues with both iput() and > vfs_fsync_range() because they call mark_inode_dirty_sync() on > I_DIRTY_TIME inodes to move them onto the writeback list so they are > appropriately expired when the inode is written back. True, we'd need to call ->lazytime_expired in the fsync path as well. While looking into this I've also noticed that lazytime is "enabled" unconditionally without a file system opt-in. That means for file systems that don't rely on ->dirty_inode it kinda "just works" except that both Teds original fix and this one break that in one way or another. This series just cleanly disables it, but Ted's two patches would fail to pass I_DIRTY_SYNC to ->write_inode. This whole area is such a mess..
