On Thu, Jul 25, 2019 at 2:08 PM syzbot <syzbot+6ff9bba63b987471b8be@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote: > > Hello, > > syzbot found the following crash on: > > HEAD commit: 6a3599ce usb-fuzzer: main usb gadget fuzzer driver > git tree: https://github.com/google/kasan.git usb-fuzzer > console output: https://syzkaller.appspot.com/x/log.txt?x=10d72ef0600000 > kernel config: https://syzkaller.appspot.com/x/.config?x=700ca426ab83faae > dashboard link: https://syzkaller.appspot.com/bug?extid=6ff9bba63b987471b8be > compiler: gcc (GCC) 9.0.0 20181231 (experimental) > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=144edb68600000 > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14cd0e64600000 > > IMPORTANT: if you fix the bug, please add the following tag to the commit: > Reported-by: syzbot+6ff9bba63b987471b8be@xxxxxxxxxxxxxxxxxxxxxxxxx > > usb 1-1: USB disconnect, device number 2 > ------------[ cut here ]------------ > ODEBUG: free active (active state 0) object type: timer_list hint: > hid_retry_timeout+0x0/0xd0 drivers/hid/usbhid/hid-core.c:716 > WARNING: CPU: 1 PID: 21 at lib/debugobjects.c:325 > debug_print_object+0x160/0x250 lib/debugobjects.c:325 > Kernel panic - not syncing: panic_on_warn set ... > CPU: 1 PID: 21 Comm: kworker/1:1 Not tainted 5.2.0-rc6+ #15 > 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+0xca/0x13e lib/dump_stack.c:113 > panic+0x292/0x6c9 kernel/panic.c:219 > __warn.cold+0x20/0x4b kernel/panic.c:576 > report_bug+0x262/0x2a0 lib/bug.c:186 > fixup_bug arch/x86/kernel/traps.c:179 [inline] > fixup_bug arch/x86/kernel/traps.c:174 [inline] > do_error_trap+0x12b/0x1e0 arch/x86/kernel/traps.c:272 > do_invalid_op+0x32/0x40 arch/x86/kernel/traps.c:291 > invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:986 > RIP: 0010:debug_print_object+0x160/0x250 lib/debugobjects.c:325 > Code: dd e0 16 ba 85 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 bf 00 00 00 48 > 8b 14 dd e0 16 ba 85 48 c7 c7 c0 0c ba 85 e8 db c7 33 ff <0f> 0b 83 05 03 > 6e 86 05 01 48 83 c4 20 5b 5d 41 5c 41 5d c3 48 89 > RSP: 0018:ffff8881d9eff710 EFLAGS: 00010086 > RAX: 0000000000000000 RBX: 0000000000000003 RCX: 0000000000000000 > RDX: 0000000000000000 RSI: ffffffff8127ef3d RDI: ffffed103b3dfed4 > RBP: 0000000000000001 R08: ffff8881d9e36000 R09: ffffed103b663ed7 > R10: ffffed103b663ed6 R11: ffff8881db31f6b7 R12: ffffffff86b04760 > R13: ffffffff812db3c0 R14: ffffffff88f4bae8 R15: ffff8881d0e1a8c8 > __debug_check_no_obj_freed lib/debugobjects.c:785 [inline] > debug_check_no_obj_freed+0x2a3/0x42e lib/debugobjects.c:817 > free_pages_prepare mm/page_alloc.c:1140 [inline] > __free_pages_ok+0x215/0x1bb0 mm/page_alloc.c:1366 > usbhid_disconnect+0x98/0xd0 drivers/hid/usbhid/hid-core.c:1414 > usb_unbind_interface+0x1bd/0x8a0 drivers/usb/core/driver.c:423 > __device_release_driver drivers/base/dd.c:1081 [inline] > device_release_driver_internal+0x404/0x4c0 drivers/base/dd.c:1112 > bus_remove_device+0x2dc/0x4a0 drivers/base/bus.c:556 > device_del+0x460/0xb80 drivers/base/core.c:2274 > usb_disable_device+0x211/0x690 drivers/usb/core/message.c:1237 > usb_disconnect+0x284/0x830 drivers/usb/core/hub.c:2199 > hub_port_connect drivers/usb/core/hub.c:4949 [inline] > hub_port_connect_change drivers/usb/core/hub.c:5213 [inline] > port_event drivers/usb/core/hub.c:5359 [inline] > hub_event+0x13bd/0x3550 drivers/usb/core/hub.c:5441 > process_one_work+0x905/0x1570 kernel/workqueue.c:2269 > worker_thread+0x96/0xe20 kernel/workqueue.c:2415 > kthread+0x30b/0x410 kernel/kthread.c:255 > ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:352 > > ====================================================== > > > --- > 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@xxxxxxxxxxxxxxxx. > > syzbot will keep track of this bug report. See: > https://goo.gl/tpsmEJ#status for how to communicate with syzbot. > syzbot can test patches for this bug, for details see: > https://goo.gl/tpsmEJ#testing-patches #syz dup: WARNING: ODEBUG bug in usbhid_disconnect (2)
