From: syzbot <syzbot+28a246747e0a465127f3@syzkaller.appspotmail.com>
To: eli.billauer@gmail.com, gregkh@linuxfoundation.org,
gustavoars@kernel.org, ingrassia@epigenesys.com,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
oneukum@suse.com, stern@rowland.harvard.edu,
syzkaller-bugs@googlegroups.com, tiwai@suse.de
Subject: memory leak in atusb_probe
Date: Fri, 13 Nov 2020 09:17:32 -0800 [thread overview]
Message-ID: <0000000000002ed0ef05b4003400@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: af5043c8 Merge tag 'acpi-5.10-rc4' of git://git.kernel.org..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10f165e6500000
kernel config: https://syzkaller.appspot.com/x/.config?x=a3f13716fa0212fd
dashboard link: https://syzkaller.appspot.com/bug?extid=28a246747e0a465127f3
compiler: gcc (GCC) 10.1.0-syz 20200507
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=155d8dba500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=153b46a1500000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+28a246747e0a465127f3@syzkaller.appspotmail.com
BUG: memory leak
unreferenced object 0xffff888109e0af00 (size 192):
comm "kworker/1:2", pid 3205, jiffies 4294942324 (age 8.180s)
hex dump (first 32 bytes):
01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 18 af e0 09 81 88 ff ff ................
backtrace:
[<0000000070ad19b0>] kmalloc include/linux/slab.h:557 [inline]
[<0000000070ad19b0>] usb_alloc_urb+0x66/0xe0 drivers/usb/core/urb.c:74
[<000000008781be0e>] atusb_alloc_urbs drivers/net/ieee802154/atusb.c:362 [inline]
[<000000008781be0e>] atusb_probe+0x158/0x820 drivers/net/ieee802154/atusb.c:1038
[<00000000cce0cf01>] usb_probe_interface+0x177/0x370 drivers/usb/core/driver.c:396
[<0000000020e0d57d>] really_probe+0x159/0x480 drivers/base/dd.c:554
[<00000000e105c1d7>] driver_probe_device+0x84/0x100 drivers/base/dd.c:738
[<0000000027607927>] __device_attach_driver+0xee/0x110 drivers/base/dd.c:844
[<000000003813d62a>] bus_for_each_drv+0xb7/0x100 drivers/base/bus.c:431
[<00000000e9e76ec4>] __device_attach+0x122/0x250 drivers/base/dd.c:912
[<00000000db4b9c2e>] bus_probe_device+0xc6/0xe0 drivers/base/bus.c:491
[<0000000004dae719>] device_add+0x5ac/0xc30 drivers/base/core.c:2936
[<000000002e126243>] usb_set_configuration+0x9de/0xb90 drivers/usb/core/message.c:2159
[<0000000076889926>] usb_generic_driver_probe+0x8c/0xc0 drivers/usb/core/generic.c:238
[<000000004ff8d735>] usb_probe_device+0x5c/0x140 drivers/usb/core/driver.c:293
[<0000000020e0d57d>] really_probe+0x159/0x480 drivers/base/dd.c:554
[<00000000e105c1d7>] driver_probe_device+0x84/0x100 drivers/base/dd.c:738
[<0000000027607927>] __device_attach_driver+0xee/0x110 drivers/base/dd.c:844
BUG: memory leak
unreferenced object 0xffff888109e0a300 (size 192):
comm "kworker/1:2", pid 3205, jiffies 4294942324 (age 8.180s)
hex dump (first 32 bytes):
01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 18 a3 e0 09 81 88 ff ff ................
backtrace:
[<0000000070ad19b0>] kmalloc include/linux/slab.h:557 [inline]
[<0000000070ad19b0>] usb_alloc_urb+0x66/0xe0 drivers/usb/core/urb.c:74
[<000000008781be0e>] atusb_alloc_urbs drivers/net/ieee802154/atusb.c:362 [inline]
[<000000008781be0e>] atusb_probe+0x158/0x820 drivers/net/ieee802154/atusb.c:1038
[<00000000cce0cf01>] usb_probe_interface+0x177/0x370 drivers/usb/core/driver.c:396
[<0000000020e0d57d>] really_probe+0x159/0x480 drivers/base/dd.c:554
[<00000000e105c1d7>] driver_probe_device+0x84/0x100 drivers/base/dd.c:738
[<0000000027607927>] __device_attach_driver+0xee/0x110 drivers/base/dd.c:844
[<000000003813d62a>] bus_for_each_drv+0xb7/0x100 drivers/base/bus.c:431
[<00000000e9e76ec4>] __device_attach+0x122/0x250 drivers/base/dd.c:912
[<00000000db4b9c2e>] bus_probe_device+0xc6/0xe0 drivers/base/bus.c:491
[<0000000004dae719>] device_add+0x5ac/0xc30 drivers/base/core.c:2936
[<000000002e126243>] usb_set_configuration+0x9de/0xb90 drivers/usb/core/message.c:2159
[<0000000076889926>] usb_generic_driver_probe+0x8c/0xc0 drivers/usb/core/generic.c:238
[<000000004ff8d735>] usb_probe_device+0x5c/0x140 drivers/usb/core/driver.c:293
[<0000000020e0d57d>] really_probe+0x159/0x480 drivers/base/dd.c:554
[<00000000e105c1d7>] driver_probe_device+0x84/0x100 drivers/base/dd.c:738
[<0000000027607927>] __device_attach_driver+0xee/0x110 drivers/base/dd.c:844
---
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-13 17:17 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=0000000000002ed0ef05b4003400@google.com \
--to=syzbot+28a246747e0a465127f3@syzkaller.appspotmail.com \
--cc=eli.billauer@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=gustavoars@kernel.org \
--cc=ingrassia@epigenesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@suse.com \
--cc=stern@rowland.harvard.edu \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tiwai@suse.de \
/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.