From: Jaegeuk Kim via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Chao Yu <chao@kernel.org>
Cc: Haofeng Li <lihaofeng@kylinos.cn>,
Haofeng Li <13266079573@163.com>,
linux-kernel@vger.kernel.org, Haofeng Li <920484857@qq.com>,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix ifolio memory leak in f2fs_move_inline_dirents error path
Date: Fri, 3 Oct 2025 03:15:31 +0000 [thread overview]
Message-ID: <aN8_05vg6Lz1eAkF@google.com> (raw)
In-Reply-To: <3bdcdb11-2d67-4842-b21c-2b41ce5faea9@kernel.org>
On 10/03, Chao Yu wrote:
> On 2025/9/30 17:16, Haofeng Li wrote:
> > From: Haofeng Li <lihaofeng@kylinos.cn>
> >
> > Fixes a memory leak issue in f2fs_move_inline_dirents() where
> > the ifolio is not properly released in certain error paths.
> >
> > Problem Analysis:
> > - In f2fs_try_convert_inline_dir(), ifolio is acquired via f2fs_get_inode_folio()
> > - When do_convert_inline_dir() fails, the caller expects ifolio to be released
> > - However, in f2fs_move_inline_dirents(), two specific error paths don't release ifolio
> >
> > Fixes: 201a05be9628a ("f2fs: add key function to handle inline dir")
> > Signed-off-by: Haofeng Li <lihaofeng@kylinos.cn>
> > ---
> > fs/f2fs/inline.c | 8 ++++++--
> > 1 file changed, 6 insertions(+), 2 deletions(-)
> >
> > diff --git a/fs/f2fs/inline.c b/fs/f2fs/inline.c
> > index 58ac831ef704..2496866fc45d 100644
> > --- a/fs/f2fs/inline.c
> > +++ b/fs/f2fs/inline.c
> > @@ -425,7 +425,7 @@ static int f2fs_move_inline_dirents(struct inode *dir, struct folio *ifolio,
> > set_new_dnode(&dn, dir, ifolio, NULL, 0);
> > err = f2fs_reserve_block(&dn, 0);
>
> f2fs_reserve_block() will call f2fs_put_dnode() in its error path, it has
> unlocked & released inode folio?
>
> > if (err)
> > - goto out;
> > + goto out_put_ifolio;
> > if (unlikely(dn.data_blkaddr != NEW_ADDR)) {
> > f2fs_put_dnode(&dn);
>
> Ditto, or am I missing something?
It seems you're right. Let me drop this patch.
>
> Thanks,
>
> > @@ -434,7 +434,7 @@ static int f2fs_move_inline_dirents(struct inode *dir, struct folio *ifolio,
> > __func__, dir->i_ino, dn.data_blkaddr);
> > f2fs_handle_error(F2FS_F_SB(folio), ERROR_INVALID_BLKADDR);
> > err = -EFSCORRUPTED;
> > - goto out;
> > + goto out_put_ifolio;
> > }
> > f2fs_folio_wait_writeback(folio, DATA, true, true);
> > @@ -479,6 +479,10 @@ static int f2fs_move_inline_dirents(struct inode *dir, struct folio *ifolio,
> > out:
> > f2fs_folio_put(folio, true);
> > return err;
> > +
> > +out_put_ifolio:
> > + f2fs_folio_put(ifolio, true);
> > + goto out;
> > }
> > static int f2fs_add_inline_entries(struct inode *dir, void *inline_dentry)
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2025-10-03 3:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-30 9:16 [f2fs-dev] [PATCH] f2fs: fix ifolio memory leak in f2fs_move_inline_dirents error path Haofeng Li via Linux-f2fs-devel
2025-09-30 10:04 ` Haofeng Li via Linux-f2fs-devel
2025-10-02 20:50 ` patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-10-03 1:39 ` Chao Yu via Linux-f2fs-devel
2025-10-03 3:15 ` Jaegeuk Kim via Linux-f2fs-devel [this message]
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=aN8_05vg6Lz1eAkF@google.com \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=13266079573@163.com \
--cc=920484857@qq.com \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=lihaofeng@kylinos.cn \
--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;
as well as URLs for NNTP newsgroup(s).