[v5.15] INFO: task hung in hub_event

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 115472395b0a Linux 5.15.104
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11669119c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=f5592cc4916e1c2f
dashboard link: https://syzkaller.appspot.com/bug?extid=abb389dcfe069bc85fcb
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/6c2c0744c7e0/disk-11547239.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7ea4c5ecca4f/vmlinux-11547239.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9a231dbcf423/bzImage-11547239.xz

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

INFO: task kworker/1:7:3697 blocked for more than 143 seconds.
Not tainted 5.15.104-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/1:7 state:D stack:19808 pid: 3697 ppid: 2 flags:0x00004000
Workqueue: usb_hub_wq hub_event
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5023 [inline]
__schedule+0x12c4/0x4590 kernel/sched/core.c:6369
schedule+0x11b/0x1f0 kernel/sched/core.c:6452
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6511
__mutex_lock_common+0xe34/0x25a0 kernel/locking/mutex.c:669
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
hub_port_connect drivers/usb/core/hub.c:5255 [inline]
hub_port_connect_change drivers/usb/core/hub.c:5502 [inline]
port_event drivers/usb/core/hub.c:5648 [inline]
hub_event+0x235a/0x56d0 drivers/usb/core/hub.c:5730
process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2306
worker_thread+0xaca/0x1280 kernel/workqueue.c:2453
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/27:
#0: ffffffff8c91b920 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by getty/3274:
#0: ffff88802417f098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffffc90002bb62e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6af/0x1da0 drivers/tty/n_tty.c:2147
2 locks held by kworker/0:3/3307:
#0: ffff888011c66538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2279
#1: ffffc90002dafd20 ((work_completion)(&rew.rew_work)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2281
5 locks held by kworker/1:5/3679:
#0: ffff888141bde538 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2279
#1: ffffc90003ccfd20 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2281
#2: ffff88801f21f220 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:760 [inline]
#2: ffff88801f21f220 (&dev->mutex){....}-{3:3}, at: hub_event+0x207/0x56d0 drivers/usb/core/hub.c:5676
#3: ffff88814847e5c0 (&port_dev->status_lock){+.+.}-{3:3}, at: usb_lock_port drivers/usb/core/hub.c:3091 [inline]
#3: ffff88814847e5c0 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_port_connect drivers/usb/core/hub.c:5254 [inline]
#3: ffff88814847e5c0 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_port_connect_change drivers/usb/core/hub.c:5502 [inline]
#3: ffff88814847e5c0 (&port_dev->status_lock){+.+.}-{3:3}, at: port_event drivers/usb/core/hub.c:5648 [inline]
#3: ffff88814847e5c0 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_event+0x2325/0x56d0 drivers/usb/core/hub.c:5730
#4: ffff88801def7868 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_port_connect drivers/usb/core/hub.c:5255 [inline]
#4: ffff88801def7868 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_port_connect_change drivers/usb/core/hub.c:5502 [inline]
#4: ffff88801def7868 (hcd->address0_mutex){+.+.}-{3:3}, at: port_event drivers/usb/core/hub.c:5648 [inline]
#4: ffff88801def7868 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_event+0x235a/0x56d0 drivers/usb/core/hub.c:5730
2 locks held by kworker/u4:5/3687:
#0: ffff888011c69138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2279
#1: ffffc90003d2fd20 ((work_completion)(&sub_info->work)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2281
5 locks held by kworker/1:7/3697:
#0: ffff888141bde538 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2279
#1: ffffc90003f8fd20 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2281
#2: ffff8881485a3220 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:760 [inline]
#2: ffff8881485a3220 (&dev->mutex){....}-{3:3}, at: hub_event+0x207/0x56d0 drivers/usb/core/hub.c:5676
#3: ffff88801f2185c0 (&port_dev->status_lock){+.+.}-{3:3}, at: usb_lock_port drivers/usb/core/hub.c:3091 [inline]
#3: ffff88801f2185c0 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_port_connect drivers/usb/core/hub.c:5254 [inline]
#3: ffff88801f2185c0 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_port_connect_change drivers/usb/core/hub.c:5502 [inline]
#3: ffff88801f2185c0 (&port_dev->status_lock){+.+.}-{3:3}, at: port_event drivers/usb/core/hub.c:5648 [inline]
#3: ffff88801f2185c0 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_event+0x2325/0x56d0 drivers/usb/core/hub.c:5730
#4: ffff88801def7868 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_port_connect drivers/usb/core/hub.c:5255 [inline]
#4: ffff88801def7868 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_port_connect_change drivers/usb/core/hub.c:5502 [inline]
#4: ffff88801def7868 (hcd->address0_mutex){+.+.}-{3:3}, at: port_event drivers/usb/core/hub.c:5648 [inline]
#4: ffff88801def7868 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_event+0x235a/0x56d0 drivers/usb/core/hub.c:5730
2 locks held by kworker/u4:17/9216:
#0: ffff888011c69138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2279
#1: ffffc9000406fd20 ((work_completion)(&sub_info->work)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2281
4 locks held by kworker/u4:1/472:
1 lock held by syz-executor.4/16314:
#0: ffffffff8c91fd70 (rcu_state.barrier_mutex){+.+.}-{3:3}, at: rcu_barrier+0x9c/0x4e0 kernel/rcu/tree.c:3994
1 lock held by syz-executor.3/16336:
#0: ffff88801b335468 (&lo->lo_mutex){+.+.}-{3:3}, at: __loop_clr_fd+0xa9/0xbe0 drivers/block/loop.c:1348
1 lock held by modprobe/16339:
#0: ffffffff8c941190 (cgroup_threadgroup_rwsem){++++}-{0:0}, at: do_exit+0x285/0x2480 kernel/exit.c:828
1 lock held by modprobe/16340:
#0: ffffffff8c941190 (cgroup_threadgroup_rwsem){++++}-{0:0}, at: do_exit+0x285/0x2480 kernel/exit.c:828
1 lock held by syz-executor.1/16342:
#0: ffffffff8c941190 (cgroup_threadgroup_rwsem){++++}-{0:0}, at: copy_process+0x2210/0x3ef0 kernel/fork.c:2299
5 locks held by kvm-nx-lpage-re/16346:
#0: ffffffff8c940fa8 (cgroup_mutex){+.+.}-{3:3}, at: cgroup_attach_task_all+0x23/0x150 kernel/cgroup/cgroup-v1.c:61
#1: ffffffff8c7b9590 (cpu_hotplug_lock){++++}-{0:0}, at: cgroup_attach_task_all+0x28/0x150 kernel/cgroup/cgroup-v1.c:62
#2: ffffffff8c941190 (cgroup_threadgroup_rwsem){++++}-{0:0}, at: cgroup_attach_task_all+0x34/0x150 kernel/cgroup/cgroup-v1.c:63
#3: ffffffff8c94d270 (&cpuset_rwsem){++++}-{0:0}, at: cpuset_can_attach+0x1e9/0x490 kernel/cgroup/cpuset.c:2197
#4: ffffffff8c91fe68 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:290 [inline]
#4: ffffffff8c91fe68 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x280/0x740 kernel/rcu/tree_exp.h:840

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

NMI backtrace for cpu 0
CPU: 0 PID: 27 Comm: khungtaskd Not tainted 5.15.104-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
nmi_cpu_backtrace+0x46a/0x4a0 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x181/0x2a0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:210 [inline]
watchdog+0xe72/0xeb0 kernel/hung_task.c:295
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 4667 Comm: kworker/1:10 Not tainted 5.15.104-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
Workqueue: events nsim_dev_trap_report_work
RIP: 0010:get_stack_info+0x3b/0xf0
Code: 89 f5 48 85 f6 74 07 48 85 ff 75 0f eb 4c 65 48 8b 2d b9 a4 d5 7e 48 85 ff 74 3f 48 89 ee 48 89 da e8 39 d8 e9 08 84 c0 74 30 <45> 31 ff 4d 85 f6 74 34 4d 8b 2e 44 8b 23 49 83 fc 40 73 4d 4d 0f
RSP: 0018:ffffc90004cc7688 EFLAGS: 00000202
RAX: 0000000004cc7701 RBX: ffffc90004cc7720 RCX: ffffc90004cc0000
RDX: ffffc90004cc7720 RSI: ffffc90004cc8000 RDI: ffffc90004cc76c0
RBP: ffff88806b779d00 R08: dffffc0000000001 R09: ffffc90004cc7720
R10: 0000000000000000 R11: dffffc0000000001 R12: ffffc90004cc7740
R13: ffffc90004cc7748 R14: ffffc90004cc7740 R15: 1ffff92000998ee9
FS: 0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f76cd757690 CR3: 000000007c11d000 CR4: 00000000003526e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__unwind_start+0x437/0x720 arch/x86/kernel/unwind_orc.c:673
unwind_start arch/x86/include/asm/unwind.h:60 [inline]
arch_stack_walk+0xdb/0x140 arch/x86/kernel/stacktrace.c:24
stack_trace_save+0x113/0x1c0 kernel/stacktrace.c:122
kasan_save_stack mm/kasan/common.c:38 [inline]
kasan_set_track mm/kasan/common.c:46 [inline]
set_alloc_info mm/kasan/common.c:434 [inline]
____kasan_kmalloc+0xba/0xf0 mm/kasan/common.c:513
kasan_kmalloc include/linux/kasan.h:264 [inline]
__kmalloc_node_track_caller+0x195/0x390 mm/slub.c:4963
kmalloc_reserve net/core/skbuff.c:356 [inline]
__alloc_skb+0x12c/0x590 net/core/skbuff.c:427
alloc_skb include/linux/skbuff.h:1166 [inline]
nsim_dev_trap_skb_build drivers/net/netdevsim/dev.c:667 [inline]
nsim_dev_trap_report drivers/net/netdevsim/dev.c:724 [inline]
nsim_dev_trap_report_work+0x25e/0xab0 drivers/net/netdevsim/dev.c:765
process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2306
worker_thread+0xaca/0x1280 kernel/workqueue.c:2453
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</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.

[syzbot]

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