From: syzbot <syzbot+bb25f85e5aa482864dc0@syzkaller.appspotmail.com>
To: crope@iki.fi, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, mchehab@kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] memory leak in airspy_probe
Date: Wed, 10 Aug 2022 19:20:28 -0700 [thread overview]
Message-ID: <0000000000001809aa05e5edcf23@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 20cf903a0c40 Merge tag 'for-6.0/dm-changes-2' of git://git..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14fbfa46080000
kernel config: https://syzkaller.appspot.com/x/.config?x=9f3121e03e34975
dashboard link: https://syzkaller.appspot.com/bug?extid=bb25f85e5aa482864dc0
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15cb43fa080000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=165877f2080000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+bb25f85e5aa482864dc0@syzkaller.appspotmail.com
BUG: memory leak
unreferenced object 0xffff88810afb7300 (size 128):
comm "kworker/0:1", pid 44, jiffies 4294946315 (age 14.410s)
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:
[<ffffffff8316980e>] kmalloc include/linux/slab.h:600 [inline]
[<ffffffff8316980e>] kzalloc include/linux/slab.h:733 [inline]
[<ffffffff8316980e>] airspy_probe+0x8e/0x200 drivers/media/usb/airspy/airspy.c:981
[<ffffffff82d83457>] usb_probe_interface+0x177/0x370 drivers/usb/core/driver.c:396
[<ffffffff8277ff2d>] call_driver_probe drivers/base/dd.c:530 [inline]
[<ffffffff8277ff2d>] really_probe+0x12d/0x390 drivers/base/dd.c:609
[<ffffffff8278024f>] __driver_probe_device+0xbf/0x140 drivers/base/dd.c:748
[<ffffffff827802fa>] driver_probe_device+0x2a/0x120 drivers/base/dd.c:778
[<ffffffff82780c46>] __device_attach_driver+0xf6/0x140 drivers/base/dd.c:901
[<ffffffff8277d127>] bus_for_each_drv+0xb7/0x100 drivers/base/bus.c:427
[<ffffffff827806d2>] __device_attach+0x102/0x2d0 drivers/base/dd.c:973
[<ffffffff8277ed96>] bus_probe_device+0xc6/0xe0 drivers/base/bus.c:487
[<ffffffff8277b152>] device_add+0x642/0xe60 drivers/base/core.c:3517
[<ffffffff82d80892>] usb_set_configuration+0x8f2/0xb80 drivers/usb/core/message.c:2170
[<ffffffff82d9121c>] usb_generic_driver_probe+0x8c/0xc0 drivers/usb/core/generic.c:238
[<ffffffff82d82b2c>] usb_probe_device+0x5c/0x140 drivers/usb/core/driver.c:293
[<ffffffff8277ff2d>] call_driver_probe drivers/base/dd.c:530 [inline]
[<ffffffff8277ff2d>] really_probe+0x12d/0x390 drivers/base/dd.c:609
[<ffffffff8278024f>] __driver_probe_device+0xbf/0x140 drivers/base/dd.c:748
[<ffffffff827802fa>] driver_probe_device+0x2a/0x120 drivers/base/dd.c:778
---
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:[~2022-08-11 2:20 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=0000000000001809aa05e5edcf23@google.com \
--to=syzbot+bb25f85e5aa482864dc0@syzkaller.appspotmail.com \
--cc=crope@iki.fi \
--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