Skip to content

Commit 13ef6bc

Browse files
ebiggersgregkh
authored andcommitted
fs: fix lazytime expiration handling in __writeback_single_inode()
commit 1e249cb upstream. When lazytime is enabled and an inode is being written due to its in-memory updated timestamps having expired, either due to a sync() or syncfs() system call or due to dirtytime_expire_interval having elapsed, the VFS needs to inform the filesystem so that the filesystem can copy the inode's timestamps out to the on-disk data structures. This is done by __writeback_single_inode() calling mark_inode_dirty_sync(), which then calls ->dirty_inode(I_DIRTY_SYNC). However, this occurs after __writeback_single_inode() has already cleared the dirty flags from ->i_state. This causes two bugs: - mark_inode_dirty_sync() redirties the inode, causing it to remain dirty. This wastefully causes the inode to be written twice. But more importantly, it breaks cases where sync_filesystem() is expected to clean dirty inodes. This includes the FS_IOC_REMOVE_ENCRYPTION_KEY ioctl (as reported at https://lore.kernel.org/r/20200306004555.GB225345@gmail.com), as well as possibly filesystem freezing (freeze_super()). - Since ->i_state doesn't contain I_DIRTY_TIME when ->dirty_inode() is called from __writeback_single_inode() for lazytime expiration, xfs_fs_dirty_inode() ignores the notification. (XFS only cares about lazytime expirations, and it assumes that i_state will contain I_DIRTY_TIME during those.) Therefore, lazy timestamps aren't persisted by sync(), syncfs(), or dirtytime_expire_interval on XFS. Fix this by moving the call to mark_inode_dirty_sync() to earlier in __writeback_single_inode(), before the dirty flags are cleared from i_state. This makes filesystems be properly notified of the timestamp expiration, and it avoids incorrectly redirtying the inode. This fixes xfstest generic/580 (which tests FS_IOC_REMOVE_ENCRYPTION_KEY) when run on ext4 or f2fs with lazytime enabled. It also fixes the new lazytime xfstest I've proposed, which reproduces the above-mentioned XFS bug (https://lore.kernel.org/r/20210105005818.92978-1-ebiggers@kernel.org). Alternatively, we could call ->dirty_inode(I_DIRTY_SYNC) directly. But due to the introduction of I_SYNC_QUEUED, mark_inode_dirty_sync() is the right thing to do because mark_inode_dirty_sync() now knows not to move the inode to a writeback list if it is currently queued for sync. Fixes: 0ae45f6 ("vfs: add support for a lazytime mount option") Cc: stable@vger.kernel.org Depends-on: 5afced3 ("writeback: Avoid skipping inode writeback") Link: https://lore.kernel.org/r/20210112190253.64307-2-ebiggers@kernel.org Suggested-by: Jan Kara <jack@suse.cz> 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> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
1 parent adc1111 commit 13ef6bc

File tree

1 file changed

+13
-11
lines changed

1 file changed

+13
-11
lines changed

fs/fs-writeback.c

Lines changed: 13 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1474,21 +1474,25 @@ __writeback_single_inode(struct inode *inode, struct writeback_control *wbc)
14741474
}
14751475

14761476
/*
1477-
* Some filesystems may redirty the inode during the writeback
1478-
* due to delalloc, clear dirty metadata flags right before
1479-
* write_inode()
1477+
* If the inode has dirty timestamps and we need to write them, call
1478+
* mark_inode_dirty_sync() to notify the filesystem about it and to
1479+
* change I_DIRTY_TIME into I_DIRTY_SYNC.
14801480
*/
1481-
spin_lock(&inode->i_lock);
1482-
1483-
dirty = inode->i_state & I_DIRTY;
14841481
if ((inode->i_state & I_DIRTY_TIME) &&
1485-
((dirty & I_DIRTY_INODE) ||
1486-
wbc->sync_mode == WB_SYNC_ALL || wbc->for_sync ||
1482+
(wbc->sync_mode == WB_SYNC_ALL || wbc->for_sync ||
14871483
time_after(jiffies, inode->dirtied_time_when +
14881484
dirtytime_expire_interval * HZ))) {
1489-
dirty |= I_DIRTY_TIME;
14901485
trace_writeback_lazytime(inode);
1486+
mark_inode_dirty_sync(inode);
14911487
}
1488+
1489+
/*
1490+
* Some filesystems may redirty the inode during the writeback
1491+
* due to delalloc, clear dirty metadata flags right before
1492+
* write_inode()
1493+
*/
1494+
spin_lock(&inode->i_lock);
1495+
dirty = inode->i_state & I_DIRTY;
14921496
inode->i_state &= ~dirty;
14931497

14941498
/*
@@ -1509,8 +1513,6 @@ __writeback_single_inode(struct inode *inode, struct writeback_control *wbc)
15091513

15101514
spin_unlock(&inode->i_lock);
15111515

1512-
if (dirty & I_DIRTY_TIME)
1513-
mark_inode_dirty_sync(inode);
15141516
/* Don't write the inode if only I_DIRTY_PAGES was set */
15151517
if (dirty & ~I_DIRTY_PAGES) {
15161518
int err = write_inode(inode, wbc);

0 commit comments

Comments
 (0)