Re: [f2fs-dev] [PATCH] f2fs: keep atomic write retry from zeroing original data
patchwork-bot+f2fs--- via Linux-f2fs-devel <[email protected]>
| Newsgroups | net.sourceforge.lists.linux-f2fs-devel,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <178153740988.3946007.10376202781077694557.git-patchwork-notify@kernel.org> |
Hello: This patch was applied to jaegeuk/f2fs.git (dev) by Jaegeuk Kim <[email protected]>: On Wed, 27 May 2026 20:06:28 +0800 you wrote: > A partial atomic write reserves a block in the COW inode before reading the > original data page for the untouched bytes in that page. > > If that read fails, write_begin returns an error but leaves the COW inode > entry as NEW_ADDR. A retry of the same partial write then finds the COW > entry, treats it as existing COW data, and f2fs_write_begin() zeroes the > whole folio because blkaddr is NEW_ADDR. > > [...] Here is the summary with links: - [f2fs-dev] f2fs: keep atomic write retry from zeroing original data https://git.kernel.org/jaegeuk/f2fs/c/b5d5ab1ebe69 You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html _______________________________________________ Linux-f2fs-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel