From: Chao Yu <chao@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Cc: chao@kernel.org
Subject: Re: [f2fs-dev] [PATCH] f2fs: avoid trying to get invalid block address
Date: Mon, 20 Jan 2025 13:27:09 +0800 [thread overview]
Message-ID: <4e1348cc-9b91-40f0-b740-d26530fac6ce@kernel.org> (raw)
In-Reply-To: <20250117220955.2482817-1-jaegeuk@kernel.org>
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 no block address allocated yet, which gives a chance to access
> a wrong block address, if the block device has some garbage data in NAT table.
>
> We need to make sure NAT table should have zero data for all the unallocated
> node ids, but also would be better to take this unnecessary path as well.
> Let's mark the faild inode as bad.
>
Needs a fixes line?
Fixes: 0abd675e97e6 ("f2fs: support plain user/group quota")
Otherwise, it looks good to me.
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
> ---
> fs/f2fs/namei.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/fs/f2fs/namei.c b/fs/f2fs/namei.c
> index 57d46e1439de..a278c7da8177 100644
> --- a/fs/f2fs/namei.c
> +++ b/fs/f2fs/namei.c
> @@ -341,6 +341,7 @@ static struct inode *f2fs_new_inode(struct mnt_idmap *idmap,
> trace_f2fs_new_inode(inode, err);
> dquot_drop(inode);
> inode->i_flags |= S_NOQUOTA;
> + make_bad_inode(inode);
> if (nid_free)
> set_inode_flag(inode, FI_FREE_NID);
> clear_nlink(inode);
next prev parent reply other threads:[~2025-01-20 5:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-17 22:09 [PATCH] f2fs: avoid trying to get invalid block address Jaegeuk Kim
2025-01-20 5:27 ` Chao Yu [this message]
2025-01-21 17:00 ` [f2fs-dev] " patchwork-bot+f2fs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4e1348cc-9b91-40f0-b740-d26530fac6ce@kernel.org \
--to=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox