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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 6c6a6c7e211c Linux 6.1.66
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10caccb6e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=ae60e3c09665494a
dashboard link: https://syzkaller.appspot.com/bug?extid=f898ddae7ec39f767bf8
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a1d0b246f59f/disk-6c6a6c7e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/777cb9cf9777/vmlinux-6c6a6c7e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/4a872139cccc/Image-6c6a6c7e.gz.xz

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

INFO: task syz-executor.2:8100 blocked for more than 143 seconds.
Not tainted 6.1.66-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.2 state:D stack:0 pid:8100 ppid:4264 flags:0x00000005
Call trace:
__switch_to+0x320/0x754 arch/arm64/kernel/process.c:553
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0xee4/0x1c98 kernel/sched/core.c:6558
schedule+0xc4/0x170 kernel/sched/core.c:6634
schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6693
__mutex_lock_common+0xbd8/0x21a0 kernel/locking/mutex.c:679
__mutex_lock kernel/locking/mutex.c:747 [inline]
mutex_lock_nested+0x38/0x44 kernel/locking/mutex.c:799
device_lock include/linux/device.h:836 [inline]
usbdev_open+0x13c/0x6c0 drivers/usb/core/devio.c:1052
chrdev_open+0x3e8/0x4fc fs/char_dev.c:414
do_dentry_open+0x734/0xfa0 fs/open.c:882
vfs_open+0x7c/0x90 fs/open.c:1013
do_open fs/namei.c:3558 [inline]
path_openat+0x1e14/0x2548 fs/namei.c:3715
do_filp_open+0x1bc/0x3cc fs/namei.c:3742
do_sys_openat2+0x128/0x3d8 fs/open.c:1318
do_sys_open fs/open.c:1334 [inline]
__do_sys_openat fs/open.c:1350 [inline]
__se_sys_openat fs/open.c:1345 [inline]
__arm64_sys_openat+0x1f0/0x240 fs/open.c:1345
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585

Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
#0: ffff8000159f4e70 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x44/0xcf4 kernel/rcu/tasks.h:516
1 lock held by rcu_tasks_trace/13:
#0: ffff8000159f5670 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x44/0xcf4 kernel/rcu/tasks.h:516
6 locks held by kworker/1:1/24:
#0: ffff0000c46a4d38 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x664/0x1404 kernel/workqueue.c:2265
#1: ffff800019ef7c20 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x6a8/0x1404 kernel/workqueue.c:2267
#2: ffff0000d165b190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:836 [inline]
#2: ffff0000d165b190 (&dev->mutex){....}-{3:3}, at: hub_event+0x1ac/0x4360 drivers/usb/core/hub.c:5758
#3: ffff0000dadaf190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:836 [inline]
#3: ffff0000dadaf190 (&dev->mutex){....}-{3:3}, at: __device_attach+0x90/0x480 drivers/base/dd.c:990
#4: ffff0000dcdf1118 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:836 [inline]
#4: ffff0000dcdf1118 (&dev->mutex){....}-{3:3}, at: __device_attach+0x90/0x480 drivers/base/dd.c:990
#5: ffff8000158a4630 (umhelper_sem){++++}-{3:3}, at: usermodehelper_read_trylock+0x12c/0x2d0 kernel/umh.c:218
1 lock held by khungtaskd/28:
#0: ffff8000159f4ca0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:305
2 locks held by getty/3981:
#0: ffff0000d6106098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x3c/0x4c drivers/tty/tty_ldsem.c:340
#1: ffff80001bc902f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1214 drivers/tty/n_tty.c:2188
2 locks held by kworker/u4:14/6651:
1 lock held by syz-executor.2/8100:
#0: ffff0000d165b190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:836 [inline]
#0: ffff0000d165b190 (&dev->mutex){....}-{3:3}, at: usbdev_open+0x13c/0x6c0 drivers/usb/core/devio.c:1052
1 lock held by syz-executor.2/8213:
#0: ffff0000d165b190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:836 [inline]
#0: ffff0000d165b190 (&dev->mutex){....}-{3:3}, at: usbdev_open+0x13c/0x6c0 drivers/usb/core/devio.c:1052
1 lock held by syz-executor.2/8276:
#0: ffff0000d165b190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:836 [inline]
#0: ffff0000d165b190 (&dev->mutex){....}-{3:3}, at: usbdev_open+0x13c/0x6c0 drivers/usb/core/devio.c:1052

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



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

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.