From: syzbot <syzbot+e1de8986786b3722050e@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
mchehab@kernel.org, syzkaller-bugs@googlegroups.com
Subject: memory leak in cinergyt2_fe_attach
Date: Thu, 12 Nov 2020 07:07:18 -0800 [thread overview]
Message-ID: <0000000000009d17f405b3ea44ab@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 3d5e28bf Merge branch 'stable/for-linus-5.10-rc2' of git:/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10bae3aa500000
kernel config: https://syzkaller.appspot.com/x/.config?x=a3f13716fa0212fd
dashboard link: https://syzkaller.appspot.com/bug?extid=e1de8986786b3722050e
compiler: gcc (GCC) 10.1.0-syz 20200507
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1781dd4e500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1636b181500000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+e1de8986786b3722050e@syzkaller.appspotmail.com
BUG: memory leak
unreferenced object 0xffff88810d626800 (size 2048):
comm "kworker/0:1", pid 7, jiffies 4294946031 (age 8.260s)
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 54 65 72 72 61 54 65 63 ........TerraTec
2f 71 61 6e 75 20 55 53 42 32 2e 30 20 48 69 67 /qanu USB2.0 Hig
backtrace:
[<000000001868ec69>] kmalloc include/linux/slab.h:552 [inline]
[<000000001868ec69>] kzalloc include/linux/slab.h:664 [inline]
[<000000001868ec69>] cinergyt2_fe_attach+0x21/0x80 drivers/media/usb/dvb-usb/cinergyT2-fe.c:271
[<0000000069d80651>] cinergyt2_frontend_attach+0x21/0x70 drivers/media/usb/dvb-usb/cinergyT2-core.c:74
[<00000000c12d6c47>] dvb_usb_adapter_frontend_init+0x11b/0x1b0 drivers/media/usb/dvb-usb/dvb-usb-dvb.c:290
[<0000000012dc4d47>] dvb_usb_adapter_init drivers/media/usb/dvb-usb/dvb-usb-init.c:84 [inline]
[<0000000012dc4d47>] dvb_usb_init drivers/media/usb/dvb-usb/dvb-usb-init.c:173 [inline]
[<0000000012dc4d47>] dvb_usb_device_init.cold+0x4d0/0x6ae drivers/media/usb/dvb-usb/dvb-usb-init.c:287
[<000000009a40ba79>] usb_probe_interface+0x177/0x370 drivers/usb/core/driver.c:396
[<0000000092664fce>] really_probe+0x159/0x480 drivers/base/dd.c:554
[<00000000ac3ae41f>] driver_probe_device+0x84/0x100 drivers/base/dd.c:738
[<000000008558e2d5>] __device_attach_driver+0xee/0x110 drivers/base/dd.c:844
[<00000000562cb0b9>] bus_for_each_drv+0xb7/0x100 drivers/base/bus.c:431
[<0000000056762cde>] __device_attach+0x122/0x250 drivers/base/dd.c:912
[<00000000412c6765>] bus_probe_device+0xc6/0xe0 drivers/base/bus.c:491
[<000000000a5960bb>] device_add+0x5ac/0xc30 drivers/base/core.c:2936
[<000000009ab6c3b2>] usb_set_configuration+0x9de/0xb90 drivers/usb/core/message.c:2159
[<00000000f4ffc3df>] usb_generic_driver_probe+0x8c/0xc0 drivers/usb/core/generic.c:238
[<00000000b38e25bd>] usb_probe_device+0x5c/0x140 drivers/usb/core/driver.c:293
[<0000000092664fce>] really_probe+0x159/0x480 drivers/base/dd.c:554
---
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
reply other threads:[~2020-11-12 15: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=0000000000009d17f405b3ea44ab@google.com \
--to=syzbot+e1de8986786b3722050e@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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).