From: syzbot <syzbot+1c70732df5fd4f0e4fbb@syzkaller.appspotmail.com>
To: eraykrdg1@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [fs?] memory leak in adfs_init_fs_context
Date: Sun, 14 Dec 2025 13:15:02 -0800 [thread overview]
Message-ID: <693f28d6.a70a0220.104cf0.032d.GAE@google.com> (raw)
In-Reply-To: <CAHxJ8O-gpHe-WzaN5pZFmsVLa_5DdY_0aKTJ6wrUaCkWEyNOSQ@mail.gmail.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
memory leak in adfs_init_fs_context
BUG: memory leak
unreferenced object 0xffff888128792680 (size 64):
comm "syz.0.17", pid 6733, jiffies 4294947442
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 c0 01 3f 00 00 00 00 00 ..........?.....
backtrace (crc 45941a6b):
kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
slab_post_alloc_hook mm/slub.c:4958 [inline]
slab_alloc_node mm/slub.c:5263 [inline]
__kmalloc_cache_noprof+0x3b2/0x570 mm/slub.c:5771
kmalloc_noprof include/linux/slab.h:957 [inline]
kzalloc_noprof include/linux/slab.h:1094 [inline]
adfs_init_fs_context+0x26/0xe0 fs/adfs/super.c:440
alloc_fs_context+0x2a0/0x6e0 fs/fs_context.c:315
do_new_mount fs/namespace.c:3692 [inline]
path_mount+0x93f/0x1320 fs/namespace.c:4022
do_mount fs/namespace.c:4035 [inline]
__do_sys_mount fs/namespace.c:4224 [inline]
__se_sys_mount fs/namespace.c:4201 [inline]
__x64_sys_mount+0x1a2/0x1e0 fs/namespace.c:4201
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xa4/0xf80 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
BUG: memory leak
unreferenced object 0xffff888128792280 (size 64):
comm "syz.0.18", pid 6736, jiffies 4294947443
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 c0 01 3f 00 00 00 00 00 ..........?.....
backtrace (crc 45941a6b):
kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
slab_post_alloc_hook mm/slub.c:4958 [inline]
slab_alloc_node mm/slub.c:5263 [inline]
__kmalloc_cache_noprof+0x3b2/0x570 mm/slub.c:5771
kmalloc_noprof include/linux/slab.h:957 [inline]
kzalloc_noprof include/linux/slab.h:1094 [inline]
adfs_init_fs_context+0x26/0xe0 fs/adfs/super.c:440
alloc_fs_context+0x2a0/0x6e0 fs/fs_context.c:315
do_new_mount fs/namespace.c:3692 [inline]
path_mount+0x93f/0x1320 fs/namespace.c:4022
do_mount fs/namespace.c:4035 [inline]
__do_sys_mount fs/namespace.c:4224 [inline]
__se_sys_mount fs/namespace.c:4201 [inline]
__x64_sys_mount+0x1a2/0x1e0 fs/namespace.c:4201
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xa4/0xf80 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
BUG: memory leak
unreferenced object 0xffff88811cb63040 (size 64):
comm "syz.0.19", pid 6739, jiffies 4294947445
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 c0 01 3f 00 00 00 00 00 ..........?.....
backtrace (crc 45941a6b):
kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
slab_post_alloc_hook mm/slub.c:4958 [inline]
slab_alloc_node mm/slub.c:5263 [inline]
__kmalloc_cache_noprof+0x3b2/0x570 mm/slub.c:5771
kmalloc_noprof include/linux/slab.h:957 [inline]
kzalloc_noprof include/linux/slab.h:1094 [inline]
adfs_init_fs_context+0x26/0xe0 fs/adfs/super.c:440
alloc_fs_context+0x2a0/0x6e0 fs/fs_context.c:315
do_new_mount fs/namespace.c:3692 [inline]
path_mount+0x93f/0x1320 fs/namespace.c:4022
do_mount fs/namespace.c:4035 [inline]
__do_sys_mount fs/namespace.c:4224 [inline]
__se_sys_mount fs/namespace.c:4201 [inline]
__x64_sys_mount+0x1a2/0x1e0 fs/namespace.c:4201
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xa4/0xf80 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
BUG: memory leak
unreferenced object 0xffff888128792f80 (size 64):
comm "syz.0.20", pid 6770, jiffies 4294948013
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 c0 01 3f 00 00 00 00 00 ..........?.....
backtrace (crc 45941a6b):
kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
slab_post_alloc_hook mm/slub.c:4958 [inline]
slab_alloc_node mm/slub.c:5263 [inline]
__kmalloc_cache_noprof+0x3b2/0x570 mm/slub.c:5771
kmalloc_noprof include/linux/slab.h:957 [inline]
kzalloc_noprof include/linux/slab.h:1094 [inline]
adfs_init_fs_context+0x26/0xe0 fs/adfs/super.c:440
alloc_fs_context+0x2a0/0x6e0 fs/fs_context.c:315
do_new_mount fs/namespace.c:3692 [inline]
path_mount+0x93f/0x1320 fs/namespace.c:4022
do_mount fs/namespace.c:4035 [inline]
__do_sys_mount fs/namespace.c:4224 [inline]
__se_sys_mount fs/namespace.c:4201 [inline]
__x64_sys_mount+0x1a2/0x1e0 fs/namespace.c:4201
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xa4/0xf80 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
BUG: memory leak
unreferenced object 0xffff88811cb63f80 (size 64):
comm "syz.0.21", pid 6772, jiffies 4294948014
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 c0 01 3f 00 00 00 00 00 ..........?.....
backtrace (crc 45941a6b):
kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
slab_post_alloc_hook mm/slub.c:4958 [inline]
slab_alloc_node mm/slub.c:5263 [inline]
__kmalloc_cache_noprof+0x3b2/0x570 mm/slub.c:5771
kmalloc_noprof include/linux/slab.h:957 [inline]
kzalloc_noprof include/linux/slab.h:1094 [inline]
adfs_init_fs_context+0x26/0xe0 fs/adfs/super.c:440
alloc_fs_context+0x2a0/0x6e0 fs/fs_context.c:315
do_new_mount fs/namespace.c:3692 [inline]
path_mount+0x93f/0x1320 fs/namespace.c:4022
do_mount fs/namespace.c:4035 [inline]
__do_sys_mount fs/namespace.c:4224 [inline]
__se_sys_mount fs/namespace.c:4201 [inline]
__x64_sys_mount+0x1a2/0x1e0 fs/namespace.c:4201
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xa4/0xf80 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
connection error: failed to recv *flatrpc.ExecutorMessageRawT: EOF
Tested on:
commit: 8f0b4cce Linux 6.19-rc1
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1275511a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=d60836e327fd6756
dashboard link: https://syzkaller.appspot.com/bug?extid=1c70732df5fd4f0e4fbb
compiler: gcc (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
Note: no patches were applied.
next parent reply other threads:[~2025-12-14 21:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHxJ8O-gpHe-WzaN5pZFmsVLa_5DdY_0aKTJ6wrUaCkWEyNOSQ@mail.gmail.com>
2025-12-14 21:15 ` syzbot [this message]
[not found] <CAHxJ8O_8-_ypES0GoCMjomJGqe7dOaXVri6DRqSwsxk52=7+XA@mail.gmail.com>
2025-12-15 0:11 ` [syzbot] [fs?] memory leak in adfs_init_fs_context syzbot
[not found] <CAHxJ8O8yTfCHD3n2P_w1G0hsgzxnsanVc=_ZAR+yeU4NwPbzSg@mail.gmail.com>
2025-12-14 22:44 ` syzbot
[not found] <CAHxJ8O_ye+G1u-ML820NOsHyAKYn4h2h7VGrd_8hAUVwyxxdAQ@mail.gmail.com>
2025-12-14 22:19 ` syzbot
[not found] <CAHxJ8O8braxW=W1O+zXD1_z-raZiWd64awv8p69Da6TEiy1oyA@mail.gmail.com>
2025-12-13 23:12 ` syzbot
2025-12-13 19:01 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=693f28d6.a70a0220.104cf0.032d.GAE@google.com \
--to=syzbot+1c70732df5fd4f0e4fbb@syzkaller.appspotmail.com \
--cc=eraykrdg1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.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 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.