From: syzbot <syzbot+4d078516add5f4f12cea@syzkaller.appspotmail.com>
To: gowtham398gs@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [btrfs?] [ext4?] [ntfs3?] memory leak in __pcs_replace_full_main
Date: Thu, 05 Nov 2026 08:15:02 -0800 [thread overview]
Message-ID: <6aecab86.ab333cca.1deac.0001.GAE@google.com> (raw)
In-Reply-To: <20261105125943.178158-1-gowtham398gs@gmail.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
memory leak in __netlink_create
BUG: memory leak
unreferenced object 0xffff8881126c5800 (size 2048):
comm "udevd", pid 4994, jiffies 4294948333
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
10 00 07 40 00 00 00 00 00 00 00 00 00 00 00 00 ...@............
backtrace (crc a071d5b):
kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
slab_post_alloc_hook mm/slub.c:4735 [inline]
slab_alloc_node mm/slub.c:5035 [inline]
__do_kmalloc_node mm/slub.c:5532 [inline]
__kmalloc_noprof+0x3ce/0x510 mm/slub.c:5558
_kmalloc_noprof include/linux/slab.h:995 [inline]
sk_prot_alloc+0xf9/0x1b0 net/core/sock.c:2281
sk_alloc+0x36/0x3e0 net/core/sock.c:2337
__netlink_create+0x3b/0xb0 net/netlink/af_netlink.c:624
netlink_create+0x1c5/0x2f0 net/netlink/af_netlink.c:682
__sock_create+0x1a9/0x2d0 net/socket.c:1679
sock_create net/socket.c:1737 [inline]
__sys_socket_create net/socket.c:1774 [inline]
__sys_socket+0xb7/0x1a0 net/socket.c:1821
__do_sys_socket net/socket.c:1835 [inline]
__se_sys_socket net/socket.c:1833 [inline]
__x64_sys_socket+0x1b/0x30 net/socket.c:1833
do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
do_syscall_64+0xe9/0x530 arch/x86/entry/syscall_64.c:84
entry_SYSCALL_64_after_hwframe+0x77/0x7f
BUG: memory leak
unreferenced object 0xffff888126e74380 (size 32):
comm "udevd", pid 4994, jiffies 4294948333
hex dump (first 32 bytes):
f8 ae 0a 00 81 88 ff ff 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 f6dd81f5):
kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
slab_post_alloc_hook mm/slub.c:4735 [inline]
slab_alloc_node mm/slub.c:5035 [inline]
__do_kmalloc_node mm/slub.c:5532 [inline]
__kmalloc_noprof+0x3ce/0x510 mm/slub.c:5558
_kmalloc_noprof include/linux/slab.h:995 [inline]
_kzalloc_noprof include/linux/slab.h:1312 [inline]
lsm_blob_alloc+0x4d/0x80 security/security.c:219
lsm_sock_alloc security/security.c:4556 [inline]
security_sk_alloc+0x2d/0x290 security/security.c:4572
sk_prot_alloc+0x114/0x1b0 net/core/sock.c:2284
sk_alloc+0x36/0x3e0 net/core/sock.c:2337
__netlink_create+0x3b/0xb0 net/netlink/af_netlink.c:624
netlink_create+0x1c5/0x2f0 net/netlink/af_netlink.c:682
__sock_create+0x1a9/0x2d0 net/socket.c:1679
sock_create net/socket.c:1737 [inline]
__sys_socket_create net/socket.c:1774 [inline]
__sys_socket+0xb7/0x1a0 net/socket.c:1821
__do_sys_socket net/socket.c:1835 [inline]
__se_sys_socket net/socket.c:1833 [inline]
__x64_sys_socket+0x1b/0x30 net/socket.c:1833
do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
do_syscall_64+0xe9/0x530 arch/x86/entry/syscall_64.c:84
entry_SYSCALL_64_after_hwframe+0x77/0x7f
BUG: memory leak
unreferenced object 0xffff888127f13800 (size 2048):
comm "udevd", pid 4994, jiffies 4294948336
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
10 00 07 40 00 00 00 00 00 00 00 00 00 00 00 00 ...@............
backtrace (crc b5cbc83d):
kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
slab_post_alloc_hook mm/slub.c:4735 [inline]
slab_alloc_node mm/slub.c:5035 [inline]
__do_kmalloc_node mm/slub.c:5532 [inline]
__kmalloc_noprof+0x3ce/0x510 mm/slub.c:5558
_kmalloc_noprof include/linux/slab.h:995 [inline]
sk_prot_alloc+0xf9/0x1b0 net/core/sock.c:2281
sk_alloc+0x36/0x3e0 net/core/sock.c:2337
__netlink_create+0x3b/0xb0 net/netlink/af_netlink.c:624
netlink_create+0x1c5/0x2f0 net/netlink/af_netlink.c:682
__sock_create+0x1a9/0x2d0 net/socket.c:1679
sock_create net/socket.c:1737 [inline]
__sys_socket_create net/socket.c:1774 [inline]
__sys_socket+0xb7/0x1a0 net/socket.c:1821
__do_sys_socket net/socket.c:1835 [inline]
__se_sys_socket net/socket.c:1833 [inline]
__x64_sys_socket+0x1b/0x30 net/socket.c:1833
do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
do_syscall_64+0xe9/0x530 arch/x86/entry/syscall_64.c:84
entry_SYSCALL_64_after_hwframe+0x77/0x7f
BUG: memory leak
unreferenced object 0xffff888126fbf9e0 (size 32):
comm "udevd", pid 4994, jiffies 4294948336
hex dump (first 32 bytes):
f8 ae 0a 00 81 88 ff ff 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 f6dd81f5):
kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
slab_post_alloc_hook mm/slub.c:4735 [inline]
slab_alloc_node mm/slub.c:5035 [inline]
__do_kmalloc_node mm/slub.c:5532 [inline]
__kmalloc_noprof+0x3ce/0x510 mm/slub.c:5558
_kmalloc_noprof include/linux/slab.h:995 [inline]
_kzalloc_noprof include/linux/slab.h:1312 [inline]
lsm_blob_alloc+0x4d/0x80 security/security.c:219
lsm_sock_alloc security/security.c:4556 [inline]
security_sk_alloc+0x2d/0x290 security/security.c:4572
sk_prot_alloc+0x114/0x1b0 net/core/sock.c:2284
sk_alloc+0x36/0x3e0 net/core/sock.c:2337
__netlink_create+0x3b/0xb0 net/netlink/af_netlink.c:624
netlink_create+0x1c5/0x2f0 net/netlink/af_netlink.c:682
__sock_create+0x1a9/0x2d0 net/socket.c:1679
sock_create net/socket.c:1737 [inline]
__sys_socket_create net/socket.c:1774 [inline]
__sys_socket+0xb7/0x1a0 net/socket.c:1821
__do_sys_socket net/socket.c:1835 [inline]
__se_sys_socket net/socket.c:1833 [inline]
__x64_sys_socket+0x1b/0x30 net/socket.c:1833
do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
do_syscall_64+0xe9/0x530 arch/x86/entry/syscall_64.c:84
entry_SYSCALL_64_after_hwframe+0x77/0x7f
BUG: memory leak
unreferenced object 0xffff888126d86000 (size 2048):
comm "udevd", pid 4994, jiffies 4294948337
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
10 00 07 40 00 00 00 00 00 00 00 00 00 00 00 00 ...@............
backtrace (crc 2985600b):
kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
slab_post_alloc_hook mm/slub.c:4735 [inline]
slab_alloc_node mm/slub.c:5035 [inline]
__do_kmalloc_node mm/slub.c:5532 [inline]
__kmalloc_noprof+0x3ce/0x510 mm/slub.c:5558
_kmalloc_noprof include/linux/slab.h:995 [inline]
sk_prot_alloc+0xf9/0x1b0 net/core/sock.c:2281
sk_alloc+0x36/0x3e0 net/core/sock.c:2337
__netlink_create+0x3b/0xb0 net/netlink/af_netlink.c:624
netlink_create+0x1c5/0x2f0 net/netlink/af_netlink.c:682
__sock_create+0x1a9/0x2d0 net/socket.c:1679
sock_create net/socket.c:1737 [inline]
__sys_socket_create net/socket.c:1774 [inline]
__sys_socket+0xb7/0x1a0 net/socket.c:1821
__do_sys_socket net/socket.c:1835 [inline]
__se_sys_socket net/socket.c:1833 [inline]
__x64_sys_socket+0x1b/0x30 net/socket.c:1833
do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
do_syscall_64+0xe9/0x530 arch/x86/entry/syscall_64.c:84
entry_SYSCALL_64_after_hwframe+0x77/0x7f
BUG: memory leak
unreferenced object 0xffff888129029720 (size 32):
comm "udevd", pid 4994, jiffies 4294948337
hex dump (first 32 bytes):
f8 ae 0a 00 81 88 ff ff 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 f6dd81f5):
kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
slab_post_alloc_hook mm/slub.c:4735 [inline]
slab_alloc_node mm/slub.c:5035 [inline]
__do_kmalloc_node mm/slub.c:5532 [inline]
__kmalloc_noprof+0x3ce/0x510 mm/slub.c:5558
_kmalloc_noprof include/linux/slab.h:995 [inline]
_kzalloc_noprof include/linux/slab.h:1312 [inline]
lsm_blob_alloc+0x4d/0x80 security/security.c:219
lsm_sock_alloc security/security.c:4556 [inline]
security_sk_alloc+0x2d/0x290 security/security.c:4572
sk_prot_alloc+0x114/0x1b0 net/core/sock.c:2284
sk_alloc+0x36/0x3e0 net/core/sock.c:2337
__netlink_create+0x3b/0xb0 net/netlink/af_netlink.c:624
netlink_create+0x1c5/0x2f0 net/netlink/af_netlink.c:682
__sock_create+0x1a9/0x2d0 net/socket.c:1679
sock_create net/socket.c:1737 [inline]
__sys_socket_create net/socket.c:1774 [inline]
__sys_socket+0xb7/0x1a0 net/socket.c:1821
__do_sys_socket net/socket.c:1835 [inline]
__se_sys_socket net/socket.c:1833 [inline]
__x64_sys_socket+0x1b/0x30 net/socket.c:1833
do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
do_syscall_64+0xe9/0x530 arch/x86/entry/syscall_64.c:84
entry_SYSCALL_64_after_hwframe+0x77/0x7f
connection error: failed to recv *flatrpc.ExecutorMessageRawT: EOF
Tested on:
commit: 05441d69 Merge tag 'cocci-7.4-rc1' of git://git.kernel..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12dde455580000
kernel config: https://syzkaller.appspot.com/x/.config?x=4361b1bb937ae1c4
dashboard link: https://syzkaller.appspot.com/bug?extid=4d078516add5f4f12cea
compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
patch: https://syzkaller.appspot.com/x/patch.diff?x=13bf59dd580000
next parent reply other threads:[~2026-11-05 16:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20261105125943.178158-1-gowtham398gs@gmail.com>
2026-11-05 16:15 ` syzbot [this message]
2026-11-04 23: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=6aecab86.ab333cca.1deac.0001.GAE@google.com \
--to=syzbot+4d078516add5f4f12cea@syzkaller.appspotmail.com \
--cc=gowtham398gs@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
all inboxes | Powered by JetHome®