Hello, syzbot found the following issue on: HEAD commit: d73dc7b182be USB: chaoskey: Fix possible deadlock chaoskey.. git tree: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing console output: https://syzkaller.appspot.com/x/log.txt?x=15e94727980000 kernel config: https://syzkaller.appspot.com/x/.config?x=4510af5d637450fb dashboard link: https://syzkaller.appspot.com/bug?extid=0f138d82bfc86d146253 compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13e94727980000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/1f9e1e81549a/disk-d73dc7b1.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/e5360843a122/vmlinux-d73dc7b1.xz kernel image: https://storage.googleapis.com/syzbot-assets/3476aef56fd6/bzImage-d73dc7b1.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+0f138d82bfc86d146253@xxxxxxxxxxxxxxxxxxxxxxxxx ------------[ cut here ]------------ ODEBUG: free active (active state 0) object: ffff888131d037c8 object type: timer_list hint: rtl_ips_nic_off_wq_callback+0x0/0x680 drivers/net/wireless/realtek/rtlwifi/ps.c:283 WARNING: CPU: 1 PID: 36 at lib/debugobjects.c:514 debug_print_object+0x1a3/0x2b0 lib/debugobjects.c:514 Modules linked in: CPU: 1 UID: 0 PID: 36 Comm: kworker/1:1 Not tainted 6.12.0-rc1-syzkaller-00028-gd73dc7b182be #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 Workqueue: usb_hub_wq hub_event RIP: 0010:debug_print_object+0x1a3/0x2b0 lib/debugobjects.c:514 Code: fc ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 75 54 48 8b 14 dd c0 fc 46 87 41 56 4c 89 e6 48 c7 c7 20 f0 46 87 e8 2e d5 c3 fe 90 <0f> 0b 90 90 58 83 05 ad 76 ff 07 01 48 83 c4 18 5b 5d 41 5c 41 5d RSP: 0000:ffffc90000267418 EFLAGS: 00010282 RAX: 0000000000000000 RBX: 0000000000000003 RCX: ffffffff811ab159 RDX: ffff888102ad57c0 RSI: ffffffff811ab166 RDI: 0000000000000001 RBP: 0000000000000001 R08: 0000000000000001 R09: 0000000000000000 R10: 0000000000000001 R11: 0000000000000001 R12: ffffffff8746f6c0 R13: ffffffff872a8e00 R14: ffffffff840306a0 R15: ffffc90000267528 FS: 0000000000000000(0000) GS:ffff8881f5900000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000055d8de234978 CR3: 0000000008ca0000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> __debug_check_no_obj_freed lib/debugobjects.c:989 [inline] debug_check_no_obj_freed+0x4b8/0x600 lib/debugobjects.c:1019 free_pages_prepare mm/page_alloc.c:1115 [inline] __free_pages_ok+0x244/0xa20 mm/page_alloc.c:1250 __folio_put+0x1cd/0x250 mm/swap.c:126 device_release+0xa1/0x240 drivers/base/core.c:2575 kobject_cleanup lib/kobject.c:689 [inline] kobject_release lib/kobject.c:720 [inline] kref_put include/linux/kref.h:65 [inline] kobject_put+0x1e4/0x5a0 lib/kobject.c:737 put_device+0x1f/0x30 drivers/base/core.c:3783 rtl_usb_disconnect+0x41c/0x5a0 drivers/net/wireless/realtek/rtlwifi/usb.c:1079 usb_unbind_interface+0x1e8/0x970 drivers/usb/core/driver.c:461 device_remove drivers/base/dd.c:569 [inline] device_remove+0x122/0x170 drivers/base/dd.c:561 __device_release_driver drivers/base/dd.c:1273 [inline] device_release_driver_internal+0x44a/0x610 drivers/base/dd.c:1296 bus_remove_device+0x22f/0x420 drivers/base/bus.c:576 device_del+0x396/0x9f0 drivers/base/core.c:3864 usb_disable_device+0x36c/0x7f0 drivers/usb/core/message.c:1418 usb_disconnect+0x2e1/0x920 drivers/usb/core/hub.c:2304 hub_port_connect drivers/usb/core/hub.c:5361 [inline] hub_port_connect_change drivers/usb/core/hub.c:5661 [inline] port_event drivers/usb/core/hub.c:5821 [inline] hub_event+0x1bed/0x4f40 drivers/usb/core/hub.c:5903 --- 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@xxxxxxxxxxxxxxxx. syzbot will keep track of this issue. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot. If the report is already addressed, let syzbot know by replying with: #syz fix: exact-commit-title If you want syzbot to run the reproducer, reply with: #syz test: git://repo/address.git branch-or-commit-hash If you attach or paste a git patch, syzbot will apply it before testing. If you want to overwrite report's subsystems, reply with: #syz set subsystems: new-subsystem (See the list of subsystem names on the web dashboard) If the report is a duplicate of another one, reply with: #syz dup: exact-subject-of-another-report If you want to undo deduplication, reply with: #syz undup
