From: syzbot <syzbot+eb71df123dc2be2c1456@syzkaller.appspotmail.com>
To: andrii@kernel.org, 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, kafai@fb.com, kpsingh@chromium.org,
kuba@kernel.org, linux-kernel@vger.kernel.org,
magnus.karlsson@intel.com, netdev@vger.kernel.org,
songliubraving@fb.com, syzkaller-bugs@googlegroups.com,
yhs@fb.com
Subject: memory leak in xdp_umem_create
Date: Fri, 23 Oct 2020 07:26:22 -0700 [thread overview]
Message-ID: <0000000000006bb5d505b2575d29@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: f804b315 Merge tag 'linux-watchdog-5.10-rc1' of git://www...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1797677f900000
kernel config: https://syzkaller.appspot.com/x/.config?x=504c0405f28172a
dashboard link: https://syzkaller.appspot.com/bug?extid=eb71df123dc2be2c1456
compiler: gcc (GCC) 10.1.0-syz 20200507
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10f27544500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12fc4de8500000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+eb71df123dc2be2c1456@syzkaller.appspotmail.com
Warning: Permanently added '10.128.10.22' (ECDSA) to the list of known hosts.
executing program
executing program
BUG: memory leak
unreferenced object 0xffff888110c1e400 (size 96):
comm "syz-executor230", pid 8462, jiffies 4294942469 (age 13.280s)
hex dump (first 32 bytes):
00 50 e0 00 00 c9 ff ff 00 00 02 00 00 00 00 00 .P..............
00 00 00 00 00 10 00 00 20 00 00 00 20 00 00 00 ........ ... ...
backtrace:
[<00000000c4608c2b>] kmalloc include/linux/slab.h:554 [inline]
[<00000000c4608c2b>] kzalloc include/linux/slab.h:666 [inline]
[<00000000c4608c2b>] xdp_umem_create+0x33/0x630 net/xdp/xdp_umem.c:229
[<00000000551a05ed>] xsk_setsockopt+0x4ad/0x590 net/xdp/xsk.c:852
[<00000000f143ff32>] __sys_setsockopt+0x1b0/0x360 net/socket.c:2132
[<0000000076c65982>] __do_sys_setsockopt net/socket.c:2143 [inline]
[<0000000076c65982>] __se_sys_setsockopt net/socket.c:2140 [inline]
[<0000000076c65982>] __x64_sys_setsockopt+0x22/0x30 net/socket.c:2140
[<00000000d47a7174>] do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
[<00000000fb8e5852>] entry_SYSCALL_64_after_hwframe+0x44/0xa9
BUG: memory leak
unreferenced object 0xffff88810e018f00 (size 256):
comm "syz-executor230", pid 8462, jiffies 4294942469 (age 13.280s)
hex dump (first 32 bytes):
00 00 4f 04 00 ea ff ff 40 00 4f 04 00 ea ff ff ..O.....@.O.....
80 00 4f 04 00 ea ff ff c0 00 4f 04 00 ea ff ff ..O.......O.....
backtrace:
[<00000000257d0c74>] kmalloc_array include/linux/slab.h:594 [inline]
[<00000000257d0c74>] kcalloc include/linux/slab.h:605 [inline]
[<00000000257d0c74>] xdp_umem_pin_pages net/xdp/xdp_umem.c:89 [inline]
[<00000000257d0c74>] xdp_umem_reg net/xdp/xdp_umem.c:207 [inline]
[<00000000257d0c74>] xdp_umem_create+0x3cc/0x630 net/xdp/xdp_umem.c:240
[<00000000551a05ed>] xsk_setsockopt+0x4ad/0x590 net/xdp/xsk.c:852
[<00000000f143ff32>] __sys_setsockopt+0x1b0/0x360 net/socket.c:2132
[<0000000076c65982>] __do_sys_setsockopt net/socket.c:2143 [inline]
[<0000000076c65982>] __se_sys_setsockopt net/socket.c:2140 [inline]
[<0000000076c65982>] __x64_sys_setsockopt+0x22/0x30 net/socket.c:2140
[<00000000d47a7174>] do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
[<00000000fb8e5852>] 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-10-23 14:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-23 14:26 syzbot [this message]
2020-10-24 16:22 ` memory leak in xdp_umem_create Magnus Karlsson
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=0000000000006bb5d505b2575d29@google.com \
--to=syzbot+eb71df123dc2be2c1456@syzkaller.appspotmail.com \
--cc=andrii@kernel.org \
--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=kafai@fb.com \
--cc=kpsingh@chromium.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yhs@fb.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.