From: syzbot <syzbot+cfa88ddd0655afa88763@syzkaller.appspotmail.com>
To: ast@kernel.org, bjorn.topel@intel.com, bpf@vger.kernel.org,
daniel@iogearbox.net, davem@davemloft.net, hawk@kernel.org,
john.fastabend@gmail.com, jonathan.lemon@gmail.com,
kuba@kernel.org, linux-kernel@vger.kernel.org,
magnus.karlsson@intel.com, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: memory leak in xskq_create
Date: Sun, 13 Dec 2020 06:53:10 -0800 [thread overview]
Message-ID: <0000000000002aca2e05b659af04@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: a68a0262 mm/madvise: remove racy mm ownership check
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=165b9413500000
kernel config: https://syzkaller.appspot.com/x/.config?x=4305fa9ea70c7a9f
dashboard link: https://syzkaller.appspot.com/bug?extid=cfa88ddd0655afa88763
compiler: gcc (GCC) 10.1.0-syz 20200507
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1180a237500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=114067cf500000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+cfa88ddd0655afa88763@syzkaller.appspotmail.com
Debian GNU/Linux 9 syzkaller ttyS0
Warning: Permanently added '10.128.0.50' (ECDSA) to the list of known hosts.
executing program
executing program
BUG: memory leak
unreferenced object 0xffff88810f897940 (size 64):
comm "syz-executor991", pid 8502, jiffies 4294942194 (age 14.080s)
hex dump (first 32 bytes):
7f 00 00 00 80 00 00 00 00 00 00 00 00 00 00 00 ................
00 a0 37 0c 81 88 ff ff 00 00 00 00 00 00 00 00 ..7.............
backtrace:
[<00000000639d0dd1>] xskq_create+0x23/0xd0 include/linux/slab.h:552
[<00000000b680b035>] xsk_init_queue net/xdp/xsk.c:508 [inline]
[<00000000b680b035>] xsk_setsockopt+0x1c4/0x590 net/xdp/xsk.c:875
[<000000002b302260>] __sys_setsockopt+0x1b0/0x360 net/socket.c:2132
[<00000000ae03723e>] __do_sys_setsockopt net/socket.c:2143 [inline]
[<00000000ae03723e>] __se_sys_setsockopt net/socket.c:2140 [inline]
[<00000000ae03723e>] __x64_sys_setsockopt+0x22/0x30 net/socket.c:2140
[<0000000005c2b4a0>] do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
[<0000000003db140f>] entry_SYSCALL_64_after_hwframe+0x44/0xa9
BUG: memory leak
unreferenced object 0xffff88810f8979c0 (size 64):
comm "syz-executor991", pid 8503, jiffies 4294942194 (age 14.080s)
hex dump (first 32 bytes):
ff 03 00 00 00 04 00 00 00 00 00 00 00 00 00 00 ................
00 00 13 12 81 88 ff ff 00 00 00 00 00 00 00 00 ................
backtrace:
[<00000000639d0dd1>] xskq_create+0x23/0xd0 include/linux/slab.h:552
[<00000000b680b035>] xsk_init_queue net/xdp/xsk.c:508 [inline]
[<00000000b680b035>] xsk_setsockopt+0x1c4/0x590 net/xdp/xsk.c:875
[<000000002b302260>] __sys_setsockopt+0x1b0/0x360 net/socket.c:2132
[<00000000ae03723e>] __do_sys_setsockopt net/socket.c:2143 [inline]
[<00000000ae03723e>] __se_sys_setsockopt net/socket.c:2140 [inline]
[<00000000ae03723e>] __x64_sys_setsockopt+0x22/0x30 net/socket.c:2140
[<0000000005c2b4a0>] do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
[<0000000003db140f>] entry_SYSCALL_64_after_hwframe+0x44/0xa9
---
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.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches
next reply other threads:[~2020-12-13 14:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-13 14:53 syzbot [this message]
2020-12-16 18:11 ` memory leak in xskq_create Peilin Ye
2020-12-17 7:12 ` Björn Töpel
2020-12-17 7:50 ` Peilin Ye
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=0000000000002aca2e05b659af04@google.com \
--to=syzbot+cfa88ddd0655afa88763@syzkaller.appspotmail.com \
--cc=ast@kernel.org \
--cc=bjorn.topel@intel.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=jonathan.lemon@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=magnus.karlsson@intel.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).