From: syzbot <syzbot+fc577f12f25f2ac3b211@syzkaller.appspotmail.com>
To: davem@davemloft.net, dsahern@gmail.com, johannes.berg@intel.com,
linux-kernel@vger.kernel.org, marcel@holtmann.org,
mkubecek@suse.cz, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com, yuehaibing@huawei.com
Subject: memory leak in genl_register_family
Date: Tue, 25 Jun 2019 04:07:07 -0700 [thread overview]
Message-ID: <000000000000f5d536058c23ed60@google.com> (raw)
Hello,
syzbot found the following crash on:
HEAD commit: 4b972a01 Linux 5.2-rc6
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1305b385a00000
kernel config: https://syzkaller.appspot.com/x/.config?x=1db8bd6825f9661c
dashboard link: https://syzkaller.appspot.com/bug?extid=fc577f12f25f2ac3b211
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15bd1385a00000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+fc577f12f25f2ac3b211@syzkaller.appspotmail.com
BUG: memory leak
unreferenced object 0xffff88812a7f0c80 (size 64):
comm "swapper/0", pid 1, jiffies 4294937561 (age 881.930s)
hex dump (first 32 bytes):
2f 64 65 76 69 63 65 73 2f 76 69 72 74 75 61 6c /devices/virtual
2f 6e 65 74 2f 6c 6f 2f 71 75 65 75 65 73 2f 74 /net/lo/queues/t
backtrace:
[<00000000d629f5fa>] kmemleak_alloc_recursive
include/linux/kmemleak.h:43 [inline]
[<00000000d629f5fa>] slab_post_alloc_hook mm/slab.h:439 [inline]
[<00000000d629f5fa>] slab_alloc mm/slab.c:3326 [inline]
[<00000000d629f5fa>] __do_kmalloc mm/slab.c:3658 [inline]
[<00000000d629f5fa>] __kmalloc+0x161/0x2c0 mm/slab.c:3669
[<000000003291d450>] kmalloc_array include/linux/slab.h:670 [inline]
[<000000003291d450>] genl_register_family net/netlink/genetlink.c:355
[inline]
[<000000003291d450>] genl_register_family+0x5e1/0x7e0
net/netlink/genetlink.c:322
[<00000000f8e2dd0d>] netlbl_unlabel_genl_init+0x15/0x17
net/netlabel/netlabel_unlabeled.c:1387
[<00000000189b4a0c>] netlbl_netlink_init+0x39/0x46
net/netlabel/netlabel_user.c:65
[<0000000083adc8f0>] netlbl_init+0x65/0xa8
net/netlabel/netlabel_kapi.c:1502
[<000000003a053024>] do_one_initcall+0x5c/0x2ca init/main.c:915
[<00000000d70991fc>] do_initcall_level init/main.c:983 [inline]
[<00000000d70991fc>] do_initcalls init/main.c:991 [inline]
[<00000000d70991fc>] do_basic_setup init/main.c:1009 [inline]
[<00000000d70991fc>] kernel_init_freeable+0x1af/0x26c init/main.c:1169
[<00000000232b80c4>] kernel_init+0x10/0x155 init/main.c:1087
[<000000006b3bb174>] ret_from_fork+0x1f/0x30
arch/x86/entry/entry_64.S:352
---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this bug, for details see:
https://goo.gl/tpsmEJ#testing-patches
reply other threads:[~2019-06-25 11:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=000000000000f5d536058c23ed60@google.com \
--to=syzbot+fc577f12f25f2ac3b211@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=johannes.berg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yuehaibing@huawei.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;
as well as URLs for NNTP newsgroup(s).