From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Chao Yu <chao@kernel.org>
Cc: linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, ebiggers@kernel.org,
jaegeuk@kernel.org,
syzbot+cf7946ab25b21abc4b66@syzkaller.appspotmail.com,
stable@kernel.org
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to avoid memory leak in f2fs_rename()
Date: Thu, 05 Mar 2026 19:10:14 +0000 [thread overview]
Message-ID: <177273781429.3248266.5417972090496758870.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260304082231.599770-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 4 Mar 2026 16:22:31 +0800 you wrote:
> syzbot reported a f2fs bug as below:
>
> BUG: memory leak
> unreferenced object 0xffff888127f70830 (size 16):
> comm "syz.0.23", pid 6144, jiffies 4294943712
> hex dump (first 16 bytes):
> 3c af 57 72 5b e6 8f ad 6e 8e fd 33 42 39 03 ff <.Wr[...n..3B9..
> backtrace (crc 925f8a80):
> kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
> slab_post_alloc_hook mm/slub.c:4520 [inline]
> slab_alloc_node mm/slub.c:4844 [inline]
> __do_kmalloc_node mm/slub.c:5237 [inline]
> __kmalloc_noprof+0x3bd/0x560 mm/slub.c:5250
> kmalloc_noprof include/linux/slab.h:954 [inline]
> fscrypt_setup_filename+0x15e/0x3b0 fs/crypto/fname.c:364
> f2fs_setup_filename+0x52/0xb0 fs/f2fs/dir.c:143
> f2fs_rename+0x159/0xca0 fs/f2fs/namei.c:961
> f2fs_rename2+0xd5/0xf20 fs/f2fs/namei.c:1308
> vfs_rename+0x7ff/0x1250 fs/namei.c:6026
> filename_renameat2+0x4f4/0x660 fs/namei.c:6144
> __do_sys_renameat2 fs/namei.c:6173 [inline]
> __se_sys_renameat2 fs/namei.c:6168 [inline]
> __x64_sys_renameat2+0x59/0x80 fs/namei.c:6168
> do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
> do_syscall_64+0xe2/0xf80 arch/x86/entry/syscall_64.c:94
> entry_SYSCALL_64_after_hwframe+0x77/0x7f
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: fix to avoid memory leak in f2fs_rename()
https://git.kernel.org/jaegeuk/f2fs/c/f1139c0b9a5c
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
prev parent reply other threads:[~2026-03-05 19:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 8:22 [f2fs-dev] [PATCH] f2fs: fix to avoid memory leak in f2fs_rename() Chao Yu via Linux-f2fs-devel
2026-03-05 19:10 ` patchwork-bot+f2fs--- 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=177273781429.3248266.5417972090496758870.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patchwork-bot+f2fs@kernel.org \
--cc=stable@kernel.org \
--cc=syzbot+cf7946ab25b21abc4b66@syzkaller.appspotmail.com \
/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