diff options
author | Lukas Czerner <lczerner@redhat.com> | 2022-08-25 12:06:57 +0200 |
---|---|---|
committer | Theodore Ts'o <tytso@mit.edu> | 2022-09-29 23:02:00 -0400 |
commit | cbfecb927f429a6fa613d74b998496bd71e4438a (patch) | |
tree | 45562ba234a8cc6d72db5953123f0600628a6a3b /fs/ext4/super.c | |
parent | 50f094a5580e6297bf10a807d16f0ee23fa576cf (diff) | |
download | linux-cbfecb927f429a6fa613d74b998496bd71e4438a.tar.gz linux-cbfecb927f429a6fa613d74b998496bd71e4438a.tar.bz2 linux-cbfecb927f429a6fa613d74b998496bd71e4438a.zip |
fs: record I_DIRTY_TIME even if inode already has I_DIRTY_INODE
Currently the I_DIRTY_TIME will never get set if the inode already has
I_DIRTY_INODE with assumption that it supersedes I_DIRTY_TIME. That's
true, however ext4 will only update the on-disk inode in
->dirty_inode(), not on actual writeback. As a result if the inode
already has I_DIRTY_INODE state by the time we get to
__mark_inode_dirty() only with I_DIRTY_TIME, the time was already filled
into on-disk inode and will not get updated until the next I_DIRTY_INODE
update, which might never come if we crash or get a power failure.
The problem can be reproduced on ext4 by running xfstest generic/622
with -o iversion mount option.
Fix it by allowing I_DIRTY_TIME to be set even if the inode already has
I_DIRTY_INODE. Also make sure that the case is properly handled in
writeback_single_inode() as well. Additionally changes in
xfs_fs_dirty_inode() was made to accommodate for I_DIRTY_TIME in flag.
Thanks Jan Kara for suggestions on how to make this work properly.
Cc: Dave Chinner <david@fromorbit.com>
Cc: Christoph Hellwig <hch@infradead.org>
Cc: stable@kernel.org
Signed-off-by: Lukas Czerner <lczerner@redhat.com>
Suggested-by: Jan Kara <jack@suse.cz>
Reviewed-by: Jan Kara <jack@suse.cz>
Link: https://lore.kernel.org/r/20220825100657.44217-1-lczerner@redhat.com
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Diffstat (limited to 'fs/ext4/super.c')
0 files changed, 0 insertions, 0 deletions