From: Eric Biggers via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: syzbot <syzbot+cf7946ab25b21abc4b66@syzkaller.appspotmail.com>,
chao@kernel.org
Cc: tytso@mit.edu, syzkaller-bugs@googlegroups.com,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-fscrypt@vger.kernel.org, jaegeuk@kernel.org
Subject: Re: [f2fs-dev] [syzbot] [fscrypt?] [f2fs?] memory leak in fscrypt_setup_filename
Date: Tue, 3 Mar 2026 16:35:51 -0800 [thread overview]
Message-ID: <20260304003551.GC57956@quark> (raw)
In-Reply-To: <69a75fe1.a70a0220.b118c.0014.GAE@google.com>
On Tue, Mar 03, 2026 at 02:25:37PM -0800, syzbot wrote:
> 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
The following commit added a call to f2fs_setup_filename() without a
matching call to f2fs_free_filename():
commit 40b2d55e045222dd6de2a54a299f682e0f954b03
Author: Chao Yu <chao@kernel.org>
Date: Wed Feb 7 15:05:48 2024 +0800
f2fs: fix to create selinux label during whiteout initialization
Chao, do you want to handle fixing this?
- Eric
_______________________________________________
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: Eric Biggers <ebiggers@kernel.org>
To: syzbot <syzbot+cf7946ab25b21abc4b66@syzkaller.appspotmail.com>,
chao@kernel.org
Cc: jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-fscrypt@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, tytso@mit.edu
Subject: Re: [syzbot] [fscrypt?] [f2fs?] memory leak in fscrypt_setup_filename
Date: Tue, 3 Mar 2026 16:35:51 -0800 [thread overview]
Message-ID: <20260304003551.GC57956@quark> (raw)
In-Reply-To: <69a75fe1.a70a0220.b118c.0014.GAE@google.com>
On Tue, Mar 03, 2026 at 02:25:37PM -0800, syzbot wrote:
> 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
The following commit added a call to f2fs_setup_filename() without a
matching call to f2fs_free_filename():
commit 40b2d55e045222dd6de2a54a299f682e0f954b03
Author: Chao Yu <chao@kernel.org>
Date: Wed Feb 7 15:05:48 2024 +0800
f2fs: fix to create selinux label during whiteout initialization
Chao, do you want to handle fixing this?
- Eric
next prev parent reply other threads:[~2026-03-04 0:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 22:25 [f2fs-dev] [syzbot] [fscrypt?] [f2fs?] memory leak in fscrypt_setup_filename syzbot
2026-03-03 22:25 ` syzbot
2026-03-04 0:35 ` Eric Biggers via Linux-f2fs-devel [this message]
2026-03-04 0:35 ` Eric Biggers
2026-03-04 1:06 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2026-03-04 1:06 ` Chao Yu
2026-03-04 7:37 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2026-03-04 7:37 ` Chao Yu
2026-03-04 8:17 ` [f2fs-dev] " syzbot
2026-03-04 8:17 ` syzbot
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=20260304003551.GC57956@quark \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+cf7946ab25b21abc4b66@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
/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.