From: syzbot <syzbot+22aec786ff221549b0ab@syzkaller.appspotmail.com>
To: andreyknvl@google.com, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
rafael@kernel.org, syzkaller-bugs@googlegroups.com
Subject: INFO: trying to register non-static key in devres_release_all
Date: Wed, 08 Apr 2020 07:17:15 -0700 [thread overview]
Message-ID: <000000000000366e8705a2c82882@google.com> (raw)
Hello,
syzbot found the following crash on:
HEAD commit: 0fa84af8 Merge tag 'usb-serial-5.7-rc1' of https://git.ker..
git tree: https://github.com/google/kasan.git usb-fuzzer
console output: https://syzkaller.appspot.com/x/log.txt?x=101ed95de00000
kernel config: https://syzkaller.appspot.com/x/.config?x=6b9c154b0c23aecf
dashboard link: https://syzkaller.appspot.com/bug?extid=22aec786ff221549b0ab
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
Unfortunately, I don't have any reproducer for this crash yet.
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+22aec786ff221549b0ab@syzkaller.appspotmail.com
usb 5-1: ath9k_htc: USB layer deinitialized
INFO: trying to register non-static key.
the code is fine but needs lockdep annotation.
turning off the locking correctness validator.
CPU: 0 PID: 5 Comm: kworker/0:0 Not tainted 5.6.0-rc7-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: usb_hub_wq hub_event
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0xef/0x16e lib/dump_stack.c:118
assign_lock_key kernel/locking/lockdep.c:880 [inline]
register_lock_class+0x1022/0x11d0 kernel/locking/lockdep.c:1189
__lock_acquire+0xfc/0x3b60 kernel/locking/lockdep.c:3836
lock_acquire+0x130/0x340 kernel/locking/lockdep.c:4484
__raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
_raw_spin_lock_irqsave+0x32/0x50 kernel/locking/spinlock.c:159
devres_release_all+0x48/0xc3 drivers/base/devres.c:528
device_release+0x39/0x200 drivers/base/core.c:1364
kobject_cleanup lib/kobject.c:693 [inline]
kobject_release lib/kobject.c:722 [inline]
kref_put include/linux/kref.h:65 [inline]
kobject_put+0x256/0x550 lib/kobject.c:739
put_device drivers/base/core.c:2599 [inline]
device_unregister+0x34/0xc0 drivers/base/core.c:2710
usb_remove_ep_devs+0x3e/0x80 drivers/usb/core/endpoint.c:215
usb_disconnect+0x4bb/0x900 drivers/usb/core/hub.c:2230
hub_port_connect drivers/usb/core/hub.c:5046 [inline]
hub_port_connect_change drivers/usb/core/hub.c:5335 [inline]
port_event drivers/usb/core/hub.c:5481 [inline]
hub_event+0x1a1d/0x4300 drivers/usb/core/hub.c:5563
process_one_work+0x94b/0x1620 kernel/workqueue.c:2266
worker_thread+0x96/0xe20 kernel/workqueue.c:2412
kthread+0x318/0x420 kernel/kthread.c:255
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:352
usb 1-1: new high-speed USB device number 3 using dummy_hcd
usb 1-1: config 1 interface 0 altsetting 64 bulk endpoint 0x82 has invalid maxpacket 1024
usb 1-1: config 1 interface 0 has no altsetting 0
usb 1-1: New USB device found, idVendor=0525, idProduct=a4a8, bcdDevice= 0.40
usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-1: Product: syz
usb 1-1: Manufacturer: 됻䘰㷹ɶⵖ빚饑傩ﱬ촨즸ꇜ嘅ၧ侓剋条꠰挸渐茭塂磈늚갑ꮜࡡĘ딽쓘ꆿꐸ黀띑薛됂쟱뽏悔㘹⍸銟䝄㜓覼룹唨ᾥ낟쀆괧ᤝ옖袵ꌢಌ넏錦ၿ⦊ᓀ䂠欫矾톰岐㐂鑉翱讒鄕䕽ꃔ鎐범瀤韽猴蕕ꁇ뻇㖭벙ⵗ䫸ἂ麈䫜鼤忬刧跣庘烊灍
usb 1-1: SerialNumber: syz
usblp: can't set desired altsetting 64 on interface 0
usb 1-1: USB disconnect, device number 3
usb 1-1: new high-speed USB device number 4 using dummy_hcd
usb 1-1: config 1 interface 0 altsetting 64 bulk endpoint 0x82 has invalid maxpacket 1024
usb 1-1: config 1 interface 0 has no altsetting 0
usb 1-1: New USB device found, idVendor=0525, idProduct=a4a8, bcdDevice= 0.40
usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-1: Product: syz
usb 1-1: Manufacturer: 됻䘰㷹ɶⵖ빚饑傩ﱬ촨즸ꇜ嘅ၧ侓剋条꠰挸渐茭塂磈늚갑ꮜࡡĘ딽쓘ꆿꐸ黀띑薛됂쟱뽏悔㘹⍸銟䝄㜓覼룹唨ᾥ낟쀆괧ᤝ옖袵ꌢಌ넏錦ၿ⦊ᓀ䂠欫矾톰岐㐂鑉翱讒鄕䕽ꃔ鎐범瀤韽猴蕕ꁇ뻇㖭벙ⵗ䫸ἂ麈䫜鼤忬刧跣庘烊灍
usb 1-1: SerialNumber: syz
usblp: can't set desired altsetting 64 on interface 0
usb 1-1: USB disconnect, device number 4
usb 6-1: new high-speed USB device number 9 using dummy_hcd
usb 6-1: config 1 interface 0 altsetting 64 bulk endpoint 0x82 has invalid maxpacket 1024
usb 6-1: config 1 interface 0 has no altsetting 0
usb 6-1: New USB device found, idVendor=0525, idProduct=a4a8, bcdDevice= 0.40
usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 6-1: Product: syz
usb 6-1: Manufacturer: 됻䘰㷹ɶⵖ빚饑傩ﱬ촨즸ꇜ嘅ၧ侓剋条꠰挸渐茭塂磈늚갑ꮜࡡĘ딽쓘ꆿꐸ黀띑薛됂쟱뽏悔㘹⍸銟䝄㜓覼룹唨ᾥ낟쀆괧ᤝ옖袵ꌢಌ넏錦ၿ⦊ᓀ䂠欫矾톰岐㐂鑉翱讒鄕䕽ꃔ鎐범瀤韽猴蕕ꁇ뻇㖭벙ⵗ䫸ἂ麈䫜鼤忬刧跣庘烊灍
usb 6-1: SerialNumber: syz
usblp: can't set desired altsetting 64 on interface 0
usb 6-1: USB disconnect, device number 9
---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
reply other threads:[~2020-04-08 14: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=000000000000366e8705a2c82882@google.com \
--to=syzbot+22aec786ff221549b0ab@syzkaller.appspotmail.com \
--cc=andreyknvl@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rafael@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).