Messages in this thread | | | Subject | Re: [f2fs-dev] [PATCH 1/2] f2fs: mark inode dirty for FI_ATOMIC_COMMITTED flag | From | patchwork-bot+f2fs@kernel ... | Date | Thu, 14 Mar 2024 16:20:31 +0000 |
| |
Hello:
This series was applied to jaegeuk/f2fs.git (dev) by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 13 Mar 2024 20:26:19 +0900 you wrote: > In f2fs_update_inode, i_size of the atomic file isn't updated until > FI_ATOMIC_COMMITTED flag is set. When committing atomic write right > after the writeback of the inode, i_size of the raw inode will not be > updated. It can cause the atomicity corruption due to a mismatch between > old file size and new data. > > To prevent the problem, let's mark inode dirty for FI_ATOMIC_COMMITTED > > [...]
Here is the summary with links: - [f2fs-dev,1/2] f2fs: mark inode dirty for FI_ATOMIC_COMMITTED flag https://git.kernel.org/jaegeuk/f2fs/c/4bf78322346f - [f2fs-dev,2/2] f2fs: truncate page cache before clearing flags when aborting atomic write https://git.kernel.org/jaegeuk/f2fs/c/74b0ebcbdde4
You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html
| |