[v6.6] INFO: task hung in usbdev_open (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: da47cbc25466 Linux 6.6.144
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13be8c32580000
kernel config: https://syzkaller.appspot.com/x/.config?x=938110aa66424b94
dashboard link: https://syzkaller.appspot.com/bug?extid=e51a313a48edef8255dc
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a9e82134d7e6/disk-da47cbc2.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/296a86743157/vmlinux-da47cbc2.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c5adb532f254/bzImage-da47cbc2.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+e51a31...@syzkaller.appspotmail.com

INFO: task syz.3.437:9388 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.3.437 state:D stack:27912 pid:9388 ppid:8227 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5381 [inline]
__schedule+0x15ae/0x4660 kernel/sched/core.c:6700
schedule+0xbd/0x170 kernel/sched/core.c:6774
schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:6833
__mutex_lock_common kernel/locking/mutex.c:679 [inline]
__mutex_lock+0x673/0xc80 kernel/locking/mutex.c:747
device_lock include/linux/device.h:1094 [inline]
usbdev_open+0x152/0x770 drivers/usb/core/devio.c:1051
chrdev_open+0x58c/0x600 fs/char_dev.c:414
do_dentry_open+0x880/0x14b0 fs/open.c:929
do_open fs/namei.c:3640 [inline]
path_openat+0x284f/0x3270 fs/namei.c:3797
do_filp_open+0x1f2/0x430 fs/namei.c:3824
do_sys_openat2+0x134/0x1d0 fs/open.c:1422
do_sys_open fs/open.c:1437 [inline]
__do_sys_openat fs/open.c:1453 [inline]
__se_sys_openat fs/open.c:1448 [inline]
__x64_sys_openat+0x139/0x160 fs/open.c:1448
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f01c135e68e
RSP: 002b:00007f01c2346b28 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007f01c23476c0 RCX: 00007f01c135e68e
RDX: 0000000000101b01 RSI: 00007f01c2346c00 RDI: ffffffffffffff9c
RBP: 00007f01c2346c00 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: cccccccccccccccd
R13: 00007f01c1626038 R14: 00007f01c1625fa0 R15: 00007ffed30a3638
</TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/29:
#0: ffffffff8d131da0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:334 [inline]
#0: ffffffff8d131da0 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:786 [inline]
#0: ffffffff8d131da0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x55/0x290 kernel/locking/lockdep.c:6633
6 locks held by kworker/1:2/969:
4 locks held by kworker/u4:7/2916:
#0: ffff8880b8e3c298 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x29/0x130 kernel/sched/core.c:559
#1: ffff8880b8e28a00 (psi_seq){-.-.}-{0:0}, at: psi_sched_switch kernel/sched/stats.h:189 [inline]
#1: ffff8880b8e28a00 (psi_seq){-.-.}-{0:0}, at: __schedule+0x21d3/0x4660 kernel/sched/core.c:6695
#2:
ffff8880b8e295d8 (&base->lock){-.-.}-{2:2}, at: lock_timer_base+0x123/0x270 kernel/time/timer.c:999
#3: ffffffff974e9c68 (&obj_hash[i].lock){-.-.}-{2:2}, at: debug_object_activate+0x6c/0x500 lib/debugobjects.c:747
2 locks held by getty/5531:
#0: ffff88802df570a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
#1: ffffc9000327b2f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x428/0x1370 drivers/tty/n_tty.c:2217
6 locks held by kworker/0:3/5811:
1 lock held by syz.3.437/9388:
#0: ffff8881423911d8 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:1094 [inline]
#0: ffff8881423911d8 (&dev->mutex){....}-{3:3}, at: usbdev_open+0x152/0x770 drivers/usb/core/devio.c:1051
2 locks held by syz.7.661/10538:
1 lock held by rm/10566:
#0: ffff8880b8f3c298 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x29/0x130 kernel/sched/core.c:559

=============================================

NMI backtrace for cpu 1
CPU: 1 PID: 29 Comm: khungtaskd Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/25/2026
Call Trace:
<TASK>
dump_stack_lvl+0x18c/0x250 lib/dump_stack.c:106
nmi_cpu_backtrace+0x3a6/0x3e0 lib/nmi_backtrace.c:113
nmi_trigger_cpumask_backtrace+0x17a/0x2f0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:160 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:222 [inline]
watchdog+0xf59/0xfa0 kernel/hung_task.c:379
kthread+0x2fa/0x390 kernel/kthread.c:388
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
</TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 2916 Comm: kworker/u4:7 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/25/2026
Workqueue: events_unbound nsim_dev_trap_report_work
RIP: 0010:lock_release+0x594/0x8c0 kernel/locking/lockdep.c:5778
Code: 00 00 00 f7 84 24 80 00 00 00 00 02 00 00 43 c6 44 2f 04 f8 75 70 f7 44 24 50 00 02 00 00 74 01 fb 48 c7 44 24 60 0e 36 e0 45 <4b> c7 04 2f 00 00 00 00 43 c7 44 2f 08 00 00 00 00 65 48 8b 04 25
RSP: 0018:ffffc9000bd079c0 EFLAGS: 00000206
RAX: 0000000000000001 RBX: 85eb391cbb93a276 RCX: 26564ada74090500
RDX: 0000000000000004 RSI: ffffffff8acadce0 RDI: ffffffff8b1cfa20
RBP: ffffc9000bd07ad8 R08: ffffffff8e8c6b2f R09: 1ffffffff1d18d65
R10: dffffc0000000000 R11: fffffbfff1d18d66 R12: ffff88802c430b80
R13: dffffc0000000000 R14: ffff88802c430ad0 R15: 1ffff920017a0f44
FS: 0000000000000000(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffdd99bf5c0 CR3: 00000000316dc000 CR4: 00000000003506f0
Call Trace:
<TASK>
__raw_spin_unlock_bh include/linux/spinlock_api_smp.h:165 [inline]
_raw_spin_unlock_bh+0x1b/0x40 kernel/locking/spinlock.c:210
spin_unlock_bh include/linux/spinlock.h:396 [inline]
nsim_dev_trap_report drivers/net/netdevsim/dev.c:820 [inline]
nsim_dev_trap_report_work+0x71b/0xa90 drivers/net/netdevsim/dev.c:851
process_one_work kernel/workqueue.c:2653 [inline]
process_scheduled_works+0xa60/0x1600 kernel/workqueue.c:2730
worker_thread+0xa5e/0xfe0 kernel/workqueue.c:2811
kthread+0x2fa/0x390 kernel/kthread.c:388
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
</TASK>


---
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 syzk...@googlegroups.com.

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 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