From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Haofeng Li <920484857@qq.com>
Cc: 13266079573@163.com, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, jaegeuk@kernel.org,
lihaofeng@kylinos.cn
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix ifolio memory leak in f2fs_move_inline_dirents error path
Date: Thu, 02 Oct 2025 20:50:08 +0000 [thread overview]
Message-ID: <175943820824.3449937.3681276954916769253.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <tencent_3FA2C956B557ED4D050EB26922B50D3CF40A@qq.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Tue, 30 Sep 2025 17:16:21 +0800 you 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
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: fix ifolio memory leak in f2fs_move_inline_dirents error path
https://git.kernel.org/jaegeuk/f2fs/c/9fc1840e0217
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
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+f2fs@kernel.org
To: Haofeng Li <920484857@qq.com>
Cc: jaegeuk@kernel.org, chao@kernel.org, lihaofeng@kylinos.cn,
13266079573@163.com, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix ifolio memory leak in f2fs_move_inline_dirents error path
Date: Thu, 02 Oct 2025 20:50:08 +0000 [thread overview]
Message-ID: <175943820824.3449937.3681276954916769253.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <tencent_3FA2C956B557ED4D050EB26922B50D3CF40A@qq.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Tue, 30 Sep 2025 17:16:21 +0800 you 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
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: fix ifolio memory leak in f2fs_move_inline_dirents error path
https://git.kernel.org/jaegeuk/f2fs/c/9fc1840e0217
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2025-10-02 20:50 UTC|newest]
Thread overview: 10+ 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 9:16 ` Haofeng Li
2025-09-30 10:04 ` [f2fs-dev] " Haofeng Li via Linux-f2fs-devel
2025-09-30 10:04 ` Haofeng Li
2025-10-02 20:50 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
2025-10-02 20:50 ` [f2fs-dev] " patchwork-bot+f2fs
2025-10-03 1:39 ` Chao Yu via Linux-f2fs-devel
2025-10-03 1:39 ` Chao Yu
2025-10-03 3:15 ` [f2fs-dev] " Jaegeuk Kim via Linux-f2fs-devel
2025-10-03 3:15 ` Jaegeuk Kim
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=175943820824.3449937.3681276954916769253.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=13266079573@163.com \
--cc=920484857@qq.com \
--cc=jaegeuk@kernel.org \
--cc=lihaofeng@kylinos.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=patchwork-bot+f2fs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.