[<prev] [next>] [day] [month] [year] [list]
Message-ID: <0000000000005f907b05bc3e584e@google.com>
Date: Fri, 26 Feb 2021 06:47:20 -0800
From: syzbot <syzbot+e7f4c64a4248a0340c37@...kaller.appspotmail.com>
To: hverkuil@...all.nl, linux-kernel@...r.kernel.org,
linux-media@...r.kernel.org, mchehab@...nel.org,
syzkaller-bugs@...glegroups.com
Subject: memory leak in hdcs_probe_1x00
Hello,
syzbot found the following issue on:
HEAD commit: 2c87f7a3 Merge tag 'pwm/for-5.12-rc1' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16400946d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=3dfc598676a6f0b5
dashboard link: https://syzkaller.appspot.com/bug?extid=e7f4c64a4248a0340c37
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=123a6632d00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1689a292d00000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+e7f4c64a4248a0340c37@...kaller.appspotmail.com
BUG: memory leak
unreferenced object 0xffff8881100c0300 (size 64):
comm "kworker/0:3", pid 3861, jiffies 4294943205 (age 14.560s)
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 08 00 00 00 ................
08 00 00 00 68 01 00 00 28 01 00 00 04 00 00 00 ....h...(.......
backtrace:
[<000000004eb4188f>] kmalloc include/linux/slab.h:554 [inline]
[<000000004eb4188f>] hdcs_probe_1x00 drivers/media/usb/gspca/stv06xx/stv06xx_hdcs.c:371 [inline]
[<000000004eb4188f>] hdcs_probe_1x00.cold+0x39/0xc1 drivers/media/usb/gspca/stv06xx/stv06xx_hdcs.c:356
[<0000000031bd6da6>] stv06xx_config+0xdf/0x190 drivers/media/usb/gspca/stv06xx/stv06xx.c:571
[<000000007be62196>] gspca_dev_probe2+0x359/0x6c5 drivers/media/usb/gspca/gspca.c:1529
[<00000000afeef2a3>] gspca_dev_probe.cold+0x42/0x4a drivers/media/usb/gspca/gspca.c:1606
[<000000006d63a9d3>] usb_probe_interface+0x177/0x370 drivers/usb/core/driver.c:396
[<000000004f1fef67>] really_probe+0x159/0x4a0 drivers/base/dd.c:554
[<00000000ced991e0>] driver_probe_device+0x84/0x100 drivers/base/dd.c:740
[<000000001687c39d>] __device_attach_driver+0xee/0x110 drivers/base/dd.c:846
[<0000000046da487b>] bus_for_each_drv+0xb7/0x100 drivers/base/bus.c:431
[<00000000df1d85bd>] __device_attach+0x122/0x250 drivers/base/dd.c:914
[<00000000fa336975>] bus_probe_device+0xc6/0xe0 drivers/base/bus.c:491
[<000000002214a827>] device_add+0x5d5/0xc40 drivers/base/core.c:3242
[<00000000782f72d5>] usb_set_configuration+0x9d9/0xb90 drivers/usb/core/message.c:2164
[<000000000815ea76>] usb_generic_driver_probe+0x8c/0xc0 drivers/usb/core/generic.c:238
[<0000000028850013>] usb_probe_device+0x5c/0x140 drivers/usb/core/driver.c:293
[<000000004f1fef67>] really_probe+0x159/0x4a0 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@...glegroups.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
Powered by blists - more mailing lists