From: syzbot <syzbot+e1c69cadec0f1a078e3d@syzkaller.appspotmail.com>
To: danielyangkang@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] [exfat?] memory leak in corrupted (2)
Date: Sat, 14 Sep 2024 23:37:03 -0700 [thread overview]
Message-ID: <00000000000034483d062222af77@google.com> (raw)
In-Reply-To: <CAGiJo8QvTyC9NpS5XMy8CzSYv1suZarwWnGdYmXAXhR+NuAhgg@mail.gmail.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
memory leak in corrupted
2024/09/15 06:35:20 executed programs: 1
2024/09/15 06:35:26 executed programs: 3
BUG: memory leak
unreferenced object 0xffff88811efdfc00 (size 96):
comm "syz-executor", pid 6043, jiffies 4294946716
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
bb bb bb bb bb 00 00 73 79 7a 30 00 00 00 00 00 .......syz0.....
backtrace (crc 3da58c63):
[<ffffffff8163e352>] kmemleak_alloc_recursive include/linux/kmemleak.h:42 [inline]
[<ffffffff8163e352>] slab_post_alloc_hook mm/slub.c:3996 [inline]
[<ffffffff8163e352>] slab_alloc_node mm/slub.c:4041 [inline]
[<ffffffff8163e352>] __kmalloc_cache_noprof+0x282/0x320 mm/slub.c:4188
[<ffffffff84a65f10>] kmalloc_noprof include/linux/slab.h:681 [inline]
[<ffffffff84a65f10>] nr_add_node+0xd0/0x1440 net/netrom/nr_route.c:185
[<ffffffff84a67ed9>] nr_rt_ioctl+0xc49/0x1710 net/netrom/nr_route.c:651
[<ffffffff84a6025f>] nr_ioctl+0x11f/0x1a0 net/netrom/af_netrom.c:1254
[<ffffffff843b1052>] sock_do_ioctl+0x82/0x1a0 net/socket.c:1222
[<ffffffff843b327e>] sock_ioctl+0x14e/0x480 net/socket.c:1341
[<ffffffff81717166>] vfs_ioctl fs/ioctl.c:51 [inline]
[<ffffffff81717166>] __do_sys_ioctl fs/ioctl.c:907 [inline]
[<ffffffff81717166>] __se_sys_ioctl fs/ioctl.c:893 [inline]
[<ffffffff81717166>] __x64_sys_ioctl+0xf6/0x150 fs/ioctl.c:893
[<ffffffff8512561e>] do_syscall_x64 arch/x86/entry/common.c:52 [inline]
[<ffffffff8512561e>] do_syscall_64+0x9e/0x1d0 arch/x86/entry/common.c:83
[<ffffffff85200130>] entry_SYSCALL_64_after_hwframe+0x77/0x7f
BUG: memory leak
unreferenced object 0xffff88811dc39ae0 (size 96):
comm "syz-executor", pid 6045, jiffies 4294946717
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
bb bb bb bb bb 00 00 73 79 7a 30 00 00 00 00 00 .......syz0.....
backtrace (crc 2e887761):
[<ffffffff8163e352>] kmemleak_alloc_recursive include/linux/kmemleak.h:42 [inline]
[<ffffffff8163e352>] slab_post_alloc_hook mm/slub.c:3996 [inline]
[<ffffffff8163e352>] slab_alloc_node mm/slub.c:4041 [inline]
[<ffffffff8163e352>] __kmalloc_cache_noprof+0x282/0x320 mm/slub.c:4188
[<ffffffff84a65f10>] kmalloc_noprof include/linux/slab.h:681 [inline]
[<ffffffff84a65f10>] nr_add_node+0xd0/0x1440 net/netrom/nr_route.c:185
[<ffffffff84a67ed9>] nr_rt_ioctl+0xc49/0x1710 net/netrom/nr_route.c:651
[<ffffffff84a6025f>] nr_ioctl+0x11f/0x1a0 net/netrom/af_netrom.c:1254
[<ffffffff843b1052>] sock_do_ioctl+0x82/0x1a0 net/socket.c:1222
[<ffffffff843b327e>] sock_ioctl+0x14e/0x480 net/socket.c:1341
[<ffffffff81717166>] vfs_ioctl fs/ioctl.c:51 [inline]
[<ffffffff81717166>] __do_sys_ioctl fs/ioctl.c:907 [inline]
[<ffffffff81717166>] __se_sys_ioctl fs/ioctl.c:893 [inline]
[<ffffffff81717166>] __x64_sys_ioctl+0xf6/0x150 fs/ioctl.c:893
[<ffffffff8512561e>] do_syscall_x64 arch/x86/entry/common.c:52 [inline]
[<ffffffff8512561e>] do_syscall_64+0x9e/0x1d0 arch/x86/entry/common.c:83
[<ffffffff85200130>] entry_SYSCALL_64_after_hwframe+0x77/0x7f
BUG: memory leak
unreferenced object 0xffff88810c3ea180 (size 96):
comm "syz-executor", pid 6049, jiffies 4294947314
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
bb bb bb bb bb 00 00 73 79 7a 30 00 00 00 00 00 .......syz0.....
backtrace (crc 7ec7dee2):
[<ffffffff8163e352>] kmemleak_alloc_recursive include/linux/kmemleak.h:42 [inline]
[<ffffffff8163e352>] slab_post_alloc_hook mm/slub.c:3996 [inline]
[<ffffffff8163e352>] slab_alloc_node mm/slub.c:4041 [inline]
[<ffffffff8163e352>] __kmalloc_cache_noprof+0x282/0x320 mm/slub.c:4188
[<ffffffff84a65f10>] kmalloc_noprof include/linux/slab.h:681 [inline]
[<ffffffff84a65f10>] nr_add_node+0xd0/0x1440 net/netrom/nr_route.c:185
[<ffffffff84a67ed9>] nr_rt_ioctl+0xc49/0x1710 net/netrom/nr_route.c:651
[<ffffffff84a6025f>] nr_ioctl+0x11f/0x1a0 net/netrom/af_netrom.c:1254
[<ffffffff843b1052>] sock_do_ioctl+0x82/0x1a0 net/socket.c:1222
[<ffffffff843b327e>] sock_ioctl+0x14e/0x480 net/socket.c:1341
[<ffffffff81717166>] vfs_ioctl fs/ioctl.c:51 [inline]
[<ffffffff81717166>] __do_sys_ioctl fs/ioctl.c:907 [inline]
[<ffffffff81717166>] __se_sys_ioctl fs/ioctl.c:893 [inline]
[<ffffffff81717166>] __x64_sys_ioctl+0xf6/0x150 fs/ioctl.c:893
[<ffffffff8512561e>] do_syscall_x64 arch/x86/entry/common.c:52 [inline]
[<ffffffff8512561e>] do_syscall_64+0x9e/0x1d0 arch/x86/entry/common.c:83
[<ffffffff85200130>] entry_SYSCALL_64_after_hwframe+0x77/0x7f
BUG: memory leak
unreferenced object 0xffff88810c32eea0 (size 96):
comm "syz-executor", pid 6051, jiffies 4294947315
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
bb bb bb bb bb 00 00 73 79 7a 30 00 00 00 00 00 .......syz0.....
backtrace (crc f02899b5):
[<ffffffff8163e352>] kmemleak_alloc_recursive include/linux/kmemleak.h:42 [inline]
[<ffffffff8163e352>] slab_post_alloc_hook mm/slub.c:3996 [inline]
[<ffffffff8163e352>] slab_alloc_node mm/slub.c:4041 [inline]
[<ffffffff8163e352>] __kmalloc_cache_noprof+0x282/0x320 mm/slub.c:4188
[<ffffffff84a65f10>] kmalloc_noprof include/linux/slab.h:681 [inline]
[<ffffffff84a65f10>] nr_add_node+0xd0/0x1440 net/netrom/nr_route.c:185
[<ffffffff84a67ed9>] nr_rt_ioctl+0xc49/0x1710 net/netrom/nr_route.c:651
[<ffffffff84a6025f>] nr_ioctl+0x11f/0x1a0 net/netrom/af_netrom.c:1254
[<ffffffff843b1052>] sock_do_ioctl+0x82/0x1a0 net/socket.c:1222
[<ffffffff843b327e>] sock_ioctl+0x14e/0x480 net/socket.c:1341
[<ffffffff81717166>] vfs_ioctl fs/ioctl.c:51 [inline]
[<ffffffff81717166>] __do_sys_ioctl fs/ioctl.c:907 [inline]
[<ffffffff81717166>] __se_sys_ioctl fs/ioctl.c:893 [inline]
[<ffffffff81717166>] __x64_sys_ioctl+0xf6/0x150 fs/ioctl.c:893
[<ffffffff8512561e>] do_syscall_x64 arch/x86/entry/common.c:52 [inline]
[<ffffffff8512561e>] do_syscall_64+0x9e/0x1d0 arch/x86/entry/common.c:83
[<ffffffff85200130>] entry_SYSCALL_64_after_hwframe+0x77/0x7f
Tested on:
commit: 0babf683 Merge tag 'pinctrl-v6.11-4' of git://git.kern..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1772f49f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=aff2ee6dd356627d
dashboard link: https://syzkaller.appspot.com/bug?extid=e1c69cadec0f1a078e3d
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=1682f49f980000
parent reply other threads:[~2024-09-15 6:37 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAGiJo8QvTyC9NpS5XMy8CzSYv1suZarwWnGdYmXAXhR+NuAhgg@mail.gmail.com>]
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=00000000000034483d062222af77@google.com \
--to=syzbot+e1c69cadec0f1a078e3d@syzkaller.appspotmail.com \
--cc=danielyangkang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox