syzbot


INFO: task hung in hub_event

Status: auto-obsoleted due to no activity on 2023/08/08 09:24
Reported-by: syzbot+499c8a30d65c6c355d6e@syzkaller.appspotmail.com
First crash: 398d, last: 369d
Similar bugs (7)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in hub_event usb 19 1653d 1828d 0/26 auto-closed as invalid on 2020/01/02 20:34
linux-4.14 INFO: task hung in hub_event 5 824d 846d 0/1 auto-closed as invalid on 2022/05/10 10:19
linux-6.1 INFO: task hung in hub_event (2) 1 206d 206d 0/3 auto-obsoleted due to no activity on 2023/12/29 05:51
upstream INFO: task hung in hub_event (2) usb 27 823d 868d 0/26 closed as invalid on 2022/02/08 09:40
linux-5.15 INFO: task hung in hub_event (2) 1 112d 112d 0/3 auto-obsoleted due to no activity on 2024/04/01 17:35
upstream INFO: task hung in hub_event (3) usb 274 10d 455d 0/26 upstream: reported on 2023/01/14 20:19
linux-5.15 INFO: task hung in hub_event 3 223d 387d 0/3 auto-obsoleted due to no activity on 2023/12/12 00:26

Sample crash report:
INFO: task kworker/0:7:13149 blocked for more than 143 seconds.
      Not tainted 6.1.23-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/0:7     state:D stack:23488 pid:13149 ppid:2      flags:0x00004000
Workqueue: usb_hub_wq hub_event
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5241 [inline]
 __schedule+0x132c/0x4330 kernel/sched/core.c:6554
 schedule+0xbf/0x180 kernel/sched/core.c:6630
 schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6689
 __mutex_lock_common+0xe2b/0x2520 kernel/locking/mutex.c:679
 __mutex_lock kernel/locking/mutex.c:747 [inline]
 mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:799
 hub_port_connect drivers/usb/core/hub.c:5252 [inline]
 hub_port_connect_change drivers/usb/core/hub.c:5499 [inline]
 port_event drivers/usb/core/hub.c:5655 [inline]
 hub_event+0x22a1/0x57b0 drivers/usb/core/hub.c:5737
 process_one_work+0x8aa/0x11f0 kernel/workqueue.c:2289
 worker_thread+0xa5f/0x1210 kernel/workqueue.c:2436
 kthread+0x268/0x300 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
 </TASK>

Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
 #0: ffffffff8cf26830 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xd20 kernel/rcu/tasks.h:510
1 lock held by rcu_tasks_trace/13:
 #0: ffffffff8cf27030 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xd20 kernel/rcu/tasks.h:510
1 lock held by khungtaskd/28:
 #0: ffffffff8cf26660 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by getty/3317:
 #0: ffff888140bbd098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:244
 #1: ffffc900031262f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6a7/0x1db0 drivers/tty/n_tty.c:2177
2 locks held by syz-fuzzer/3634:
5 locks held by kworker/u4:22/6499:
 #0: ffff888012606938 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work+0x77a/0x11f0
 #1: ffffc9000c67fd20 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work+0x7bd/0x11f0 kernel/workqueue.c:2264
 #2: ffffffff8e07dbd0 (pernet_ops_rwsem){++++}-{3:3}, at: cleanup_net+0xf1/0xb60 net/core/net_namespace.c:563
 #3: ffffffff8e089f88 (rtnl_mutex){+.+.}-{3:3}, at: ip_tunnel_delete_nets+0xc9/0x330 net/ipv4/ip_tunnel.c:1121
 #4: ffffffff8cf2bc38 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:292 [inline]
 #4: ffffffff8cf2bc38 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x3b0/0x8a0 kernel/rcu/tree_exp.h:948
5 locks held by kworker/0:7/13149:
 #0: ffff888145e55138 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x77a/0x11f0
 #1: ffffc9000c48fd20 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x7bd/0x11f0 kernel/workqueue.c:2264
 #2: ffff888022ec5190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:836 [inline]
 #2: ffff888022ec5190 (&dev->mutex){....}-{3:3}, at: hub_event+0x20e/0x57b0 drivers/usb/core/hub.c:5683
 #3: ffff888022ee04f8 (&port_dev->status_lock){+.+.}-{3:3}, at: usb_lock_port drivers/usb/core/hub.c:3105 [inline]
 #3: ffff888022ee04f8 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_port_connect drivers/usb/core/hub.c:5251 [inline]
 #3: ffff888022ee04f8 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_port_connect_change drivers/usb/core/hub.c:5499 [inline]
 #3: ffff888022ee04f8 (&port_dev->status_lock){+.+.}-{3:3}, at: port_event drivers/usb/core/hub.c:5655 [inline]
 #3: ffff888022ee04f8 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_event+0x2278/0x57b0 drivers/usb/core/hub.c:5737
 #4: ffff88801deaca68 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_port_connect drivers/usb/core/hub.c:5252 [inline]
 #4: ffff88801deaca68 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_port_connect_change drivers/usb/core/hub.c:5499 [inline]
 #4: ffff88801deaca68 (hcd->address0_mutex){+.+.}-{3:3}, at: port_event drivers/usb/core/hub.c:5655 [inline]
 #4: ffff88801deaca68 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_event+0x22a1/0x57b0 drivers/usb/core/hub.c:5737
5 locks held by kworker/1:12/26477:
 #0: ffff888145e55138 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x77a/0x11f0
 #1: ffffc90006547d20 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x7bd/0x11f0 kernel/workqueue.c:2264
 #2: ffff888022eeb190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:836 [inline]
 #2: ffff888022eeb190 (&dev->mutex){....}-{3:3}, at: hub_event+0x20e/0x57b0 drivers/usb/core/hub.c:5683
 #3: ffff888022eee4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: usb_lock_port drivers/usb/core/hub.c:3105 [inline]
 #3: ffff888022eee4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_port_connect drivers/usb/core/hub.c:5251 [inline]
 #3: ffff888022eee4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_port_connect_change drivers/usb/core/hub.c:5499 [inline]
 #3: ffff888022eee4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: port_event drivers/usb/core/hub.c:5655 [inline]
 #3: ffff888022eee4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_event+0x2278/0x57b0 drivers/usb/core/hub.c:5737
 #4: ffff88801deaca68 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_port_connect drivers/usb/core/hub.c:5252 [inline]
 #4: ffff88801deaca68 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_port_connect_change drivers/usb/core/hub.c:5499 [inline]
 #4: ffff88801deaca68 (hcd->address0_mutex){+.+.}-{3:3}, at: port_event drivers/usb/core/hub.c:5655 [inline]
 #4: ffff88801deaca68 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_event+0x22a1/0x57b0 drivers/usb/core/hub.c:5737
2 locks held by kworker/1:3/26280:
 #0: ffff888012466538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x77a/0x11f0
 #1: ffffc90004457d20 ((work_completion)(&rew->rew_work)){+.+.}-{0:0}, at: process_one_work+0x7bd/0x11f0 kernel/workqueue.c:2264
2 locks held by sed/27479:

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

NMI backtrace for cpu 1
CPU: 1 PID: 28 Comm: khungtaskd Not tainted 6.1.23-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/30/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+0x4e1/0x560 lib/nmi_backtrace.c:111
 nmi_trigger_cpumask_backtrace+0x1b0/0x3f0 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:220 [inline]
 watchdog+0xf18/0xf60 kernel/hung_task.c:377
 kthread+0x268/0x300 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
 </TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 56 Comm: kworker/u4:4 Not tainted 6.1.23-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/30/2023
Workqueue: bat_events batadv_nc_worker
RIP: 0010:check_preemption_disabled+0x19/0x110 lib/smp_processor_id.c:14
Code: cc 48 c7 c7 80 b7 3c 8b 48 c7 c6 c0 b7 3c 8b eb 00 41 57 41 56 41 54 53 48 83 ec 10 65 48 8b 04 25 28 00 00 00 48 89 44 24 08 <65> 8b 1d 78 06 84 75 65 8b 05 21 5c 84 75 a9 ff ff ff 7f 74 22 65
RSP: 0018:ffffc90001577a88 EFLAGS: 00000086
RAX: 42d48a93ca407500 RBX: ffff8880181de200 RCX: ffffc90001577b03
RDX: 0000000000000002 RSI: ffffffff8aebd760 RDI: ffffffff8b3cb7e0
RBP: ffffc90001577be8 R08: dffffc0000000000 R09: fffffbfff1ca4dee
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff920002aef64
R13: 0000000000000246 R14: ffffc90001577b50 R15: dffffc0000000000
FS:  0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055fd225e8950 CR3: 000000000cc8e000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 lockdep_recursion_finish kernel/locking/lockdep.c:467 [inline]
 lock_release+0x5cb/0xa20 kernel/locking/lockdep.c:5691
 rcu_read_unlock include/linux/rcupdate.h:780 [inline]
 batadv_nc_purge_orig_hash net/batman-adv/network-coding.c:412 [inline]
 batadv_nc_worker+0x239/0x5b0 net/batman-adv/network-coding.c:719
 process_one_work+0x8aa/0x11f0 kernel/workqueue.c:2289
 worker_thread+0xa5f/0x1210 kernel/workqueue.c:2436
 kthread+0x268/0x300 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
 </TASK>

Crashes (2):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/04/10 09:23 linux-6.1.y 543aff194ab6 71147e29 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in hub_event
2023/03/12 18:32 linux-6.1.y 1cc3fcf63192 5205ef30 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in hub_event
* Struck through repros no longer work on HEAD.