From: syzbot <syzbot+b4d54814b339b5c6bbd4@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
linux-usb@vger.kernel.org, mchehab@kernel.org, royale@zerezo.com,
syzkaller-bugs@googlegroups.com
Subject: memory leak in zr364xx_probe
Date: Wed, 23 Dec 2020 07:25:17 -0800 [thread overview]
Message-ID: <0000000000006b86be05b7234cc1@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 3644e2d2 mm/filemap: fix infinite loop in generic_file_buf..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16f80eff500000
kernel config: https://syzkaller.appspot.com/x/.config?x=37c889fb8b2761af
dashboard link: https://syzkaller.appspot.com/bug?extid=b4d54814b339b5c6bbd4
compiler: gcc (GCC) 10.1.0-syz 20200507
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1089df07500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1671c77f500000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+b4d54814b339b5c6bbd4@syzkaller.appspotmail.com
BUG: memory leak
unreferenced object 0xffffc90000e71000 (size 200704):
comm "kworker/0:2", pid 3653, jiffies 4294942426 (age 13.820s)
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 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:
[<00000000110a155e>] __vmalloc_node_range+0x3a5/0x410 mm/vmalloc.c:2585
[<000000008a1ee970>] __vmalloc_node mm/vmalloc.c:2617 [inline]
[<000000008a1ee970>] vmalloc+0x49/0x50 mm/vmalloc.c:2650
[<00000000a6a3abfa>] zr364xx_board_init drivers/media/usb/zr364xx/zr364xx.c:1348 [inline]
[<00000000a6a3abfa>] zr364xx_probe+0x60b/0x833 drivers/media/usb/zr364xx/zr364xx.c:1509
[<0000000014a572f5>] usb_probe_interface+0x177/0x370 drivers/usb/core/driver.c:396
[<00000000f30ee977>] really_probe+0x159/0x480 drivers/base/dd.c:561
[<00000000ddb29374>] driver_probe_device+0x84/0x100 drivers/base/dd.c:745
[<0000000073c89cb9>] __device_attach_driver+0xee/0x110 drivers/base/dd.c:851
[<000000009f56a99c>] bus_for_each_drv+0xb7/0x100 drivers/base/bus.c:431
[<00000000848d591a>] __device_attach+0x122/0x250 drivers/base/dd.c:919
[<00000000168be5bb>] bus_probe_device+0xc6/0xe0 drivers/base/bus.c:491
[<00000000464f40a6>] device_add+0x5be/0xc30 drivers/base/core.c:3091
[<000000008c75a2b5>] usb_set_configuration+0x9d9/0xb90 drivers/usb/core/message.c:2164
[<00000000071d14a5>] usb_generic_driver_probe+0x8c/0xc0 drivers/usb/core/generic.c:238
[<00000000f325b973>] usb_probe_device+0x5c/0x140 drivers/usb/core/driver.c:293
[<00000000f30ee977>] really_probe+0x159/0x480 drivers/base/dd.c:561
[<00000000ddb29374>] driver_probe_device+0x84/0x100 drivers/base/dd.c:745
---
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-23 15:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-23 15:25 syzbot [this message]
2020-12-30 21:10 ` memory leak in zr364xx_probe Andy Shevchenko
2020-12-31 20:47 ` Ezequiel Garcia
2020-12-31 20:56 ` syzbot
2021-01-05 15:02 ` Andy Shevchenko
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=0000000000006b86be05b7234cc1@google.com \
--to=syzbot+b4d54814b339b5c6bbd4@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=royale@zerezo.com \
--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).