From: Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>
To: "syzkaller-bugs@googlegroups.com"
<syzkaller-bugs@googlegroups.com>,
"frank.li@vivo.com" <frank.li@vivo.com>,
"glaubitz@physik.fu-berlin.de" <glaubitz@physik.fu-berlin.de>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"slava@dubeyko.com" <slava@dubeyko.com>,
"syzbot+ad45f827c88778ff7df6@syzkaller.appspotmail.com"
<syzbot+ad45f827c88778ff7df6@syzkaller.appspotmail.com>
Subject: Re: [syzbot] [hfs?] memory leak in hfs_init_fs_context
Date: Thu, 13 Nov 2025 21:47:14 +0000 [thread overview]
Message-ID: <f8b383fda0c5202bdd68418afccfe258a962e244.camel@ibm.com> (raw)
In-Reply-To: <69155e34.050a0220.3565dc.0019.GAE@google.com>
Issue has been created:
https://github.com/hfs-linux-kernel/hfs-linux-kernel/issues/239
Thanks,
Slava.
On Wed, 2025-11-12 at 20:27 -0800, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 4ea7c1717f3f Merge tag 'for-linus' of git://git.kernel.org..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=17346c12580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=cb128cd5cb439809
> dashboard link: https://syzkaller.appspot.com/bug?extid=ad45f827c88778ff7df6
> compiler: gcc (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=143f5c12580000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17c9a7cd980000
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/1f8cf51c9042/disk-4ea7c171.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/6f227246b5b7/vmlinux-4ea7c171.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/f935766a00b3/bzImage-4ea7c171.xz
> mounted in repro: https://storage.googleapis.com/syzbot-assets/bee9311f4026/mount_4.gz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+ad45f827c88778ff7df6@syzkaller.appspotmail.com
>
> BUG: memory leak
> unreferenced object 0xffff888111778c00 (size 512):
> comm "syz.0.17", pid 6092, jiffies 4294942644
> 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 00 00 00 00 00 00 00 00 ................
> backtrace (crc eb1d7412):
> kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
> slab_post_alloc_hook mm/slub.c:4979 [inline]
> slab_alloc_node mm/slub.c:5284 [inline]
> __kmalloc_cache_noprof+0x3a6/0x5b0 mm/slub.c:5762
> kmalloc_noprof include/linux/slab.h:957 [inline]
> kzalloc_noprof include/linux/slab.h:1094 [inline]
> hfs_init_fs_context+0x24/0xd0 fs/hfs/super.c:411
> alloc_fs_context+0x214/0x430 fs/fs_context.c:315
> do_new_mount fs/namespace.c:3707 [inline]
> path_mount+0x93c/0x12e0 fs/namespace.c:4037
> do_mount fs/namespace.c:4050 [inline]
> __do_sys_mount fs/namespace.c:4238 [inline]
> __se_sys_mount fs/namespace.c:4215 [inline]
> __x64_sys_mount+0x1a2/0x1e0 fs/namespace.c:4215
> do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
> do_syscall_64+0xa4/0xfa0 arch/x86/entry/syscall_64.c:94
> entry_SYSCALL_64_after_hwframe+0x77/0x7f
>
> BUG: memory leak
> unreferenced object 0xffff88810a2e8800 (size 512):
> comm "syz.0.18", pid 6098, jiffies 4294942646
> 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 00 00 00 00 00 00 00 00 ................
> backtrace (crc eb1d7412):
> kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
> slab_post_alloc_hook mm/slub.c:4979 [inline]
> slab_alloc_node mm/slub.c:5284 [inline]
> __kmalloc_cache_noprof+0x3a6/0x5b0 mm/slub.c:5762
> kmalloc_noprof include/linux/slab.h:957 [inline]
> kzalloc_noprof include/linux/slab.h:1094 [inline]
> hfs_init_fs_context+0x24/0xd0 fs/hfs/super.c:411
> alloc_fs_context+0x214/0x430 fs/fs_context.c:315
> do_new_mount fs/namespace.c:3707 [inline]
> path_mount+0x93c/0x12e0 fs/namespace.c:4037
> do_mount fs/namespace.c:4050 [inline]
> __do_sys_mount fs/namespace.c:4238 [inline]
> __se_sys_mount fs/namespace.c:4215 [inline]
> __x64_sys_mount+0x1a2/0x1e0 fs/namespace.c:4215
> do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
> do_syscall_64+0xa4/0xfa0 arch/x86/entry/syscall_64.c:94
> entry_SYSCALL_64_after_hwframe+0x77/0x7f
>
> BUG: memory leak
> unreferenced object 0xffff88810a2e8e00 (size 512):
> comm "syz.0.19", pid 6102, jiffies 4294942648
> 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 00 00 00 00 00 00 00 00 ................
> backtrace (crc eb1d7412):
> kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
> slab_post_alloc_hook mm/slub.c:4979 [inline]
> slab_alloc_node mm/slub.c:5284 [inline]
> __kmalloc_cache_noprof+0x3a6/0x5b0 mm/slub.c:5762
> kmalloc_noprof include/linux/slab.h:957 [inline]
> kzalloc_noprof include/linux/slab.h:1094 [inline]
> hfs_init_fs_context+0x24/0xd0 fs/hfs/super.c:411
> alloc_fs_context+0x214/0x430 fs/fs_context.c:315
> do_new_mount fs/namespace.c:3707 [inline]
> path_mount+0x93c/0x12e0 fs/namespace.c:4037
> do_mount fs/namespace.c:4050 [inline]
> __do_sys_mount fs/namespace.c:4238 [inline]
> __se_sys_mount fs/namespace.c:4215 [inline]
> __x64_sys_mount+0x1a2/0x1e0 fs/namespace.c:4215
> do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
> do_syscall_64+0xa4/0xfa0 arch/x86/entry/syscall_64.c:94
> entry_SYSCALL_64_after_hwframe+0x77/0x7f
>
> BUG: memory leak
> unreferenced object 0xffff8881263ed600 (size 512):
> comm "syz.0.20", pid 6125, jiffies 4294943177
> 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 00 00 00 00 00 00 00 00 ................
> backtrace (crc eb1d7412):
> kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
> slab_post_alloc_hook mm/slub.c:4979 [inline]
> slab_alloc_node mm/slub.c:5284 [inline]
> __kmalloc_cache_noprof+0x3a6/0x5b0 mm/slub.c:5762
> kmalloc_noprof include/linux/slab.h:957 [inline]
> kzalloc_noprof include/linux/slab.h:1094 [inline]
> hfs_init_fs_context+0x24/0xd0 fs/hfs/super.c:411
> alloc_fs_context+0x214/0x430 fs/fs_context.c:315
> do_new_mount fs/namespace.c:3707 [inline]
> path_mount+0x93c/0x12e0 fs/namespace.c:4037
> do_mount fs/namespace.c:4050 [inline]
> __do_sys_mount fs/namespace.c:4238 [inline]
> __se_sys_mount fs/namespace.c:4215 [inline]
> __x64_sys_mount+0x1a2/0x1e0 fs/namespace.c:4215
> do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
> do_syscall_64+0xa4/0xfa0 arch/x86/entry/syscall_64.c:94
> entry_SYSCALL_64_after_hwframe+0x77/0x7f
>
> BUG: memory leak
> unreferenced object 0xffff88810db18c00 (size 512):
> comm "syz.0.21", pid 6127, jiffies 4294943179
> 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 00 00 00 00 00 00 00 00 ................
> backtrace (crc eb1d7412):
> kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
> slab_post_alloc_hook mm/slub.c:4979 [inline]
> slab_alloc_node mm/slub.c:5284 [inline]
> __kmalloc_cache_noprof+0x3a6/0x5b0 mm/slub.c:5762
> kmalloc_noprof include/linux/slab.h:957 [inline]
> kzalloc_noprof include/linux/slab.h:1094 [inline]
> hfs_init_fs_context+0x24/0xd0 fs/hfs/super.c:411
> alloc_fs_context+0x214/0x430 fs/fs_context.c:315
> do_new_mount fs/namespace.c:3707 [inline]
> path_mount+0x93c/0x12e0 fs/namespace.c:4037
> do_mount fs/namespace.c:4050 [inline]
> __do_sys_mount fs/namespace.c:4238 [inline]
> __se_sys_mount fs/namespace.c:4215 [inline]
> __x64_sys_mount+0x1a2/0x1e0 fs/namespace.c:4215
> do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
> do_syscall_64+0xa4/0xfa0 arch/x86/entry/syscall_64.c:94
> entry_SYSCALL_64_after_hwframe+0x77/0x7f
>
> connection error: failed to recv *flatrpc.ExecutorMessageRawT: EOF
>
>
> ---
> This report is generated by a bot. It may contain errors.
> See https://goo.gl/tpsmEJ for more information about syzbot.
> syzbot engineers can be reached at syzkaller@googlegroups.com.
>
> syzbot will keep track of this issue. See:
> https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
>
> If the report is already addressed, let syzbot know by replying with:
> #syz fix: exact-commit-title
>
> If you want syzbot to run the reproducer, reply with:
> #syz test: git://repo/address.git branch-or-commit-hash
> If you attach or paste a git patch, syzbot will apply it before testing.
>
> If you want to overwrite report's subsystems, reply with:
> #syz set subsystems: new-subsystem
> (See the list of subsystem names on the web dashboard)
>
> If the report is a duplicate of another one, reply with:
> #syz dup: exact-subject-of-another-report
>
> If you want to undo deduplication, reply with:
> #syz undup
--
Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>
next prev parent reply other threads:[~2025-11-13 21:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 4:27 [syzbot] [hfs?] memory leak in hfs_init_fs_context syzbot
2025-11-13 21:47 ` Viacheslav Dubeyko [this message]
2025-11-14 1:24 ` Mehdi Ben Hadj Khelifa
2025-11-14 2:03 ` [syzbot] [hfs?] memory leak in hfs_init_fs_context syzbot
2025-11-14 3:18 ` Mehdi Ben Hadj Khelifa
2025-11-14 3:00 ` [syzbot] [hfs?] memory leak in hfs_init_fs_context syzbot
2025-11-14 5:12 ` [PATCH] fs/super: fix memory leak of s_fs_info on setup_bdev_super failure Mehdi Ben Hadj Khelifa
2025-11-14 4:26 ` [syzbot] [hfs?] memory leak in hfs_init_fs_context syzbot
2025-11-14 11:55 ` [PATCH] fs/super: fix memory leak of s_fs_info on setup_bdev_super failure Christian Brauner
2025-11-14 16:05 ` Mehdi Ben Hadj Khelifa
2025-11-14 17:15 ` Mehdi Ben Hadj Khelifa
2025-11-19 13:43 ` Christian Brauner
2025-11-19 14:13 ` [syzbot] [hfs?] memory leak in hfs_init_fs_context syzbot
2025-11-19 14:16 ` Christian Brauner
2025-11-19 15:08 ` syzbot
2025-11-14 16:01 ` Mehdi Ben Hadj Khelifa
2025-11-14 15:29 ` [syzbot] [hfs?] memory leak in hfs_init_fs_context syzbot
2025-11-18 17:00 ` Mehdi Ben Hadj Khelifa
2025-11-18 17:15 ` [syzbot] [hfs?] memory leak in hfs_init_fs_context syzbot
2025-11-18 18:27 ` Mehdi Ben Hadj Khelifa
2025-11-18 17:40 ` Al Viro
2025-11-18 20:32 ` [syzbot] [hfs?] memory leak in hfs_init_fs_context syzbot
2025-11-18 19:21 ` Mehdi Ben Hadj Khelifa
2025-11-18 20:32 ` [syzbot] [hfs?] memory leak in hfs_init_fs_context syzbot
2025-11-19 5:31 ` Mehdi Ben Hadj Khelifa
2025-11-19 5:19 ` [syzbot] [hfs?] memory leak in hfs_init_fs_context 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=f8b383fda0c5202bdd68418afccfe258a962e244.camel@ibm.com \
--to=slava.dubeyko@ibm.com \
--cc=frank.li@vivo.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=slava@dubeyko.com \
--cc=syzbot+ad45f827c88778ff7df6@syzkaller.appspotmail.com \
--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.