Re: [f2fs-dev] [PATCH] f2fs: avoid trying to get invalid block address

2025-01-21 Thread patchwork-bot+f2fs--- via Linux-f2fs-devel
Hello: This patch was applied to jaegeuk/f2fs.git (dev) by Jaegeuk Kim : On Fri, 17 Jan 2025 22:09:55 + you wrote: > In f2fs_new_inode(), if we fail to get a new inode, we go iput(), followed by > f2fs_evict_inode(). If the inode is not marked as bad, it'll try to call > f2fs_remove_inode_pag

Re: [f2fs-dev] [PATCH] f2fs: avoid trying to get invalid block address

2025-01-19 Thread Chao Yu via Linux-f2fs-devel
On 1/18/25 06:09, Jaegeuk Kim via Linux-f2fs-devel wrote: In f2fs_new_inode(), if we fail to get a new inode, we go iput(), followed by f2fs_evict_inode(). If the inode is not marked as bad, it'll try to call f2fs_remove_inode_page() which tries to read the inode block given node id. But, there's

[f2fs-dev] [PATCH] f2fs: avoid trying to get invalid block address

2025-01-17 Thread Jaegeuk Kim via Linux-f2fs-devel
In f2fs_new_inode(), if we fail to get a new inode, we go iput(), followed by f2fs_evict_inode(). If the inode is not marked as bad, it'll try to call f2fs_remove_inode_page() which tries to read the inode block given node id. But, there's no block address allocated yet, which gives a chance to acc