Re: [f2fs-dev] [PATCH v2] f2fs: dirty directory inodes on mtime/ctime update
| Newsgroups | org.kernel.vger.stable,net.sourceforge.lists.linux-f2fs-devel,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <178596484313.530543.9698147873901986563.git-patchwork-notify@kernel.org> |
Hello: This patch was applied to jaegeuk/f2fs.git (dev) by Jaegeuk Kim <[email protected]>: On Tue, 23 Jun 2026 06:34:28 +0000 you wrote: > Xfstests generic/547 sometimes fail with mismatched directory metadata > before and after a power failure. This happens because when a directory > entry is added, renamed, or deleted, its mtime and ctime are updated and > the inode is marked dirty via > f2fs_mark_inode_dirty_sync(dir, sync=false). The sync=false flag means > the dirty inode is not added to the global DIRTY_META list. Therefore, > subsequent checkpoints skip flushing these updated directory blocks, > causing directory timestamps to revert to stale values after a sudden > power failure. > > [...] Here is the summary with links: - [f2fs-dev,v2] f2fs: dirty directory inodes on mtime/ctime update https://git.kernel.org/jaegeuk/f2fs/c/9ec09d5f4b31 You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html