Re: [PATCH v3] f2fs: fix valid block count leak on data block allocation failure
patchwork-bot+f2fs--- via Linux-f2fs-devel <[email protected]>
| Newsgroups | gmane.linux.file-systems.f2fs,gmane.linux.kernel,gmane.linux.kernel.stable |
|---|---|
| Message-ID | <178596484763.530543.1976176179653312885.git-patchwork-notify@kernel.org> |
Hello: This patch was applied to jaegeuk/f2fs.git (dev) by Jaegeuk Kim <[email protected]>: On Tue, 4 Aug 2026 08:54:02 +0800 you wrote: > In __allocate_data_block(), when allocating a new data block > (dn->data_blkaddr == NULL_ADDR), inc_valid_block_count() is > called first to increment total_valid_block_count and i_blocks. > If the subsequent f2fs_allocate_data_block() fails, the function > returns the error directly without rolling back the > already-incremented block counts, causing a permanent leak. > > [...] Here is the summary with links: - [f2fs-dev,v3] f2fs: fix valid block count leak on data block allocation failure https://git.kernel.org/jaegeuk/f2fs/c/0f9af07ecc1a You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html