From: syzbot <syzbot+3f2d46b6e62b8dd546d3@syzkaller.appspotmail.com>
To: kartikey406@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [hams?] memory leak in nr_add_node
Date: Fri, 16 Jan 2026 02:02:02 -0800 [thread overview]
Message-ID: <696a0c9a.050a0220.58bed.0047.GAE@google.com> (raw)
In-Reply-To: <20260116093944.1224799-1-kartikey406@gmail.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
memory leak in nr_add_node
BUG: memory leak
unreferenced object 0xffff88811385dec0 (size 64):
comm "syz.0.17", pid 6752, jiffies 4294948986
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
cc cc cc cc cc cc 02 00 00 00 00 00 00 00 00 00 ................
backtrace (crc 21d35625):
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]
nr_add_node+0x7f3/0x1600 net/netrom/nr_route.c:153
nr_rt_ioctl+0xaec/0x1410 net/netrom/nr_route.c:682
nr_ioctl+0x11f/0x1a0 net/netrom/af_netrom.c:1257
sock_do_ioctl+0x84/0x1a0 net/socket.c:1254
sock_ioctl+0x149/0x480 net/socket.c:1375
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:597 [inline]
__se_sys_ioctl fs/ioctl.c:583 [inline]
__x64_sys_ioctl+0xf4/0x140 fs/ioctl.c:583
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 0xffff88811385d980 (size 64):
comm "syz.0.18", pid 6754, jiffies 4294949002
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
cc cc cc cc cc cc 02 00 00 00 00 00 00 00 00 00 ................
backtrace (crc 564d84d5):
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]
nr_add_node+0x7f3/0x1600 net/netrom/nr_route.c:153
nr_rt_ioctl+0xaec/0x1410 net/netrom/nr_route.c:682
nr_ioctl+0x11f/0x1a0 net/netrom/af_netrom.c:1257
sock_do_ioctl+0x84/0x1a0 net/socket.c:1254
sock_ioctl+0x149/0x480 net/socket.c:1375
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:597 [inline]
__se_sys_ioctl fs/ioctl.c:583 [inline]
__x64_sys_ioctl+0xf4/0x140 fs/ioctl.c:583
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 0xffff88810a38c900 (size 64):
comm "syz.0.19", pid 6756, jiffies 4294949018
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
cc cc cc cc cc cc 02 00 00 00 00 00 00 00 00 00 ................
backtrace (crc cde8c8ba):
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]
nr_add_node+0x7f3/0x1600 net/netrom/nr_route.c:153
nr_rt_ioctl+0xaec/0x1410 net/netrom/nr_route.c:682
nr_ioctl+0x11f/0x1a0 net/netrom/af_netrom.c:1257
sock_do_ioctl+0x84/0x1a0 net/socket.c:1254
sock_ioctl+0x149/0x480 net/socket.c:1375
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:597 [inline]
__se_sys_ioctl fs/ioctl.c:583 [inline]
__x64_sys_ioctl+0xf4/0x140 fs/ioctl.c:583
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: 983d014a kernel: modules: Add SPDX license identifier ..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10b55522580000
kernel config: https://syzkaller.appspot.com/x/.config?x=87bc41cae23d2144
dashboard link: https://syzkaller.appspot.com/bug?extid=3f2d46b6e62b8dd546d3
compiler: gcc (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=13b3339a580000
next parent reply other threads:[~2026-01-16 10:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260116093944.1224799-1-kartikey406@gmail.com>
2026-01-16 10:02 ` syzbot [this message]
2026-01-17 14:26 Testing for netrom: fix memory leak in nr_add_node Prithvi Tambewagh
2026-01-17 17:00 ` [syzbot] [hams?] " syzbot
[not found] <20260116125146.1226609-1-kartikey406@gmail.com>
2026-01-16 14:04 ` syzbot
[not found] <20260116085932.1223370-1-kartikey406@gmail.com>
2026-01-16 9:15 ` syzbot
[not found] <20260116082820.1222181-1-kartikey406@gmail.com>
2026-01-16 8:52 ` syzbot
[not found] <20260116074227.1221301-1-kartikey406@gmail.com>
2026-01-16 8:03 ` syzbot
[not found] <20260116034008.1209650-1-kartikey406@gmail.com>
2026-01-16 4:49 ` syzbot
[not found] <20260116021908.1208112-1-kartikey406@gmail.com>
2026-01-16 3:02 ` syzbot
-- strict thread matches above, loose matches on Subject: below --
2026-01-15 20:04 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=696a0c9a.050a0220.58bed.0047.GAE@google.com \
--to=syzbot+3f2d46b6e62b8dd546d3@syzkaller.appspotmail.com \
--cc=kartikey406@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