syzbot


INFO: task hung in hub_event (3)

Status: upstream: reported on 2023/01/14 20:19
Subsystems: usb
[Documentation on labels]
Reported-by: syzbot+a7edecbf389d11a369d4@syzkaller.appspotmail.com
First crash: 1242d, last: 2d12h
Discussions (10)
Title Replies (including bot) Last reply
[syzbot] Monthly usb report (May 2024) 0 (1) 2024/05/10 08:47
[syzbot] Monthly usb report (Apr 2024) 0 (1) 2024/04/08 12:51
[syzbot] Monthly usb report (Mar 2024) 0 (1) 2024/03/08 08:53
[syzbot] Monthly usb report (Feb 2024) 0 (1) 2024/02/05 20:59
[syzbot] Monthly usb report (Jan 2024) 0 (1) 2024/01/05 13:17
[syzbot] Monthly usb report (Dec 2023) 0 (1) 2023/12/05 09:53
[syzbot] Monthly usb report (Nov 2023) 0 (1) 2023/11/03 20:48
[syzbot] Monthly usb report (May 2023) 0 (1) 2023/05/31 12:38
[syzbot] Monthly usb report 12 (17) 2023/04/10 16:42
[syzbot] INFO: task hung in hub_event (3) 0 (1) 2023/01/14 20:19
Similar bugs (10)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in hub_event usb 1 19 2111d 2286d 0/29 auto-closed as invalid on 2020/01/02 20:34
linux-4.14 INFO: task hung in hub_event 1 5 1282d 1304d 0/1 auto-closed as invalid on 2022/05/10 10:19
linux-5.15 INFO: task hung in hub_event (4) 1 3 82d 96d 0/3 upstream: reported on 2025/04/10 12:17
linux-6.1 INFO: task hung in hub_event (2) 1 1 664d 664d 0/3 auto-obsoleted due to no activity on 2023/12/29 05:51
upstream INFO: task hung in hub_event (2) usb 1 27 1281d 1326d 0/29 closed as invalid on 2022/02/08 09:40
linux-5.15 INFO: task hung in hub_event (2) 1 1 570d 570d 0/3 auto-obsoleted due to no activity on 2024/04/01 17:35
linux-6.1 INFO: task hung in hub_event (3) 1 8 99d 102d 0/3 upstream: reported on 2025/04/04 18:12
linux-5.15 INFO: task hung in hub_event (3) 1 1 359d 359d 0/3 auto-obsoleted due to no activity on 2024/10/29 18:51
linux-5.15 INFO: task hung in hub_event 1 3 682d 845d 0/3 auto-obsoleted due to no activity on 2023/12/12 00:26
linux-6.1 INFO: task hung in hub_event 1 2 827d 856d 0/3 auto-obsoleted due to no activity on 2023/08/08 09:24

Sample crash report:
INFO: task kworker/1:0:24 blocked for more than 143 seconds.
      Not tainted 6.16.0-rc5-syzkaller-00266-g3f31a806a62e #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/1:0     state:D stack:22872 pid:24    tgid:24    ppid:2      task_flags:0x4208060 flags:0x00004000
Workqueue: usb_hub_wq hub_event
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5397 [inline]
 __schedule+0x116a/0x5de0 kernel/sched/core.c:6786
 __schedule_loop kernel/sched/core.c:6864 [inline]
 schedule+0xe7/0x3a0 kernel/sched/core.c:6879
 schedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:6936
 __mutex_lock_common kernel/locking/mutex.c:679 [inline]
 __mutex_lock+0x6c7/0xb90 kernel/locking/mutex.c:747
 hub_port_connect drivers/usb/core/hub.c:5464 [inline]
 hub_port_connect_change drivers/usb/core/hub.c:5706 [inline]
 port_event drivers/usb/core/hub.c:5866 [inline]
 hub_event+0x292b/0x4fa0 drivers/usb/core/hub.c:5948
 process_one_work+0x9cf/0x1b70 kernel/workqueue.c:3238
 process_scheduled_works kernel/workqueue.c:3321 [inline]
 worker_thread+0x6c8/0xf10 kernel/workqueue.c:3402
 kthread+0x3c5/0x780 kernel/kthread.c:464
 ret_from_fork+0x5d7/0x6f0 arch/x86/kernel/process.c:148
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>

Showing all locks held in the system:
5 locks held by kworker/0:1/10:
 #0: ffff888140ad3948 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x12a2/0x1b70 kernel/workqueue.c:3213
 #1: ffffc900000f7d10 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x929/0x1b70 kernel/workqueue.c:3214
 #2: ffff88814573f198 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:884 [inline]
 #2: ffff88814573f198 (&dev->mutex){....}-{4:4}, at: hub_event+0x1c0/0x4fa0 drivers/usb/core/hub.c:5894
 #3: ffff88802a7e2510 (&port_dev->status_lock){+.+.}-{4:4}, at: usb_lock_port drivers/usb/core/hub.c:3251 [inline]
 #3: ffff88802a7e2510 (&port_dev->status_lock){+.+.}-{4:4}, at: hub_port_connect drivers/usb/core/hub.c:5463 [inline]
 #3: ffff88802a7e2510 (&port_dev->status_lock){+.+.}-{4:4}, at: hub_port_connect_change drivers/usb/core/hub.c:5706 [inline]
 #3: ffff88802a7e2510 (&port_dev->status_lock){+.+.}-{4:4}, at: port_event drivers/usb/core/hub.c:5866 [inline]
 #3: ffff88802a7e2510 (&port_dev->status_lock){+.+.}-{4:4}, at: hub_event+0x2906/0x4fa0 drivers/usb/core/hub.c:5948
 #4: ffff888144ff8668 (hcd->address0_mutex){+.+.}-{4:4}, at: hub_port_connect drivers/usb/core/hub.c:5464 [inline]
 #4: ffff888144ff8668 (hcd->address0_mutex){+.+.}-{4:4}, at: hub_port_connect_change drivers/usb/core/hub.c:5706 [inline]
 #4: ffff888144ff8668 (hcd->address0_mutex){+.+.}-{4:4}, at: port_event drivers/usb/core/hub.c:5866 [inline]
 #4: ffff888144ff8668 (hcd->address0_mutex){+.+.}-{4:4}, at: hub_event+0x292b/0x4fa0 drivers/usb/core/hub.c:5948
5 locks held by kworker/1:0/24:
 #0: ffff888140ad3948 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x12a2/0x1b70 kernel/workqueue.c:3213
 #1: ffffc900001e7d10 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x929/0x1b70 kernel/workqueue.c:3214
 #2: ffff888145730198 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:884 [inline]
 #2: ffff888145730198 (&dev->mutex){....}-{4:4}, at: hub_event+0x1c0/0x4fa0 drivers/usb/core/hub.c:5894
 #3: ffff888145734510 (&port_dev->status_lock){+.+.}-{4:4}, at: usb_lock_port drivers/usb/core/hub.c:3251 [inline]
 #3: ffff888145734510 (&port_dev->status_lock){+.+.}-{4:4}, at: hub_port_connect drivers/usb/core/hub.c:5463 [inline]
 #3: ffff888145734510 (&port_dev->status_lock){+.+.}-{4:4}, at: hub_port_connect_change drivers/usb/core/hub.c:5706 [inline]
 #3: ffff888145734510 (&port_dev->status_lock){+.+.}-{4:4}, at: port_event drivers/usb/core/hub.c:5866 [inline]
 #3: ffff888145734510 (&port_dev->status_lock){+.+.}-{4:4}, at: hub_event+0x2906/0x4fa0 drivers/usb/core/hub.c:5948
 #4: ffff888144ff8668 (hcd->address0_mutex){+.+.}-{4:4}, at: hub_port_connect drivers/usb/core/hub.c:5464 [inline]
 #4: ffff888144ff8668 (hcd->address0_mutex){+.+.}-{4:4}, at: hub_port_connect_change drivers/usb/core/hub.c:5706 [inline]
 #4: ffff888144ff8668 (hcd->address0_mutex){+.+.}-{4:4}, at: port_event drivers/usb/core/hub.c:5866 [inline]
 #4: ffff888144ff8668 (hcd->address0_mutex){+.+.}-{4:4}, at: hub_event+0x292b/0x4fa0 drivers/usb/core/hub.c:5948
1 lock held by khungtaskd/31:
 #0: ffffffff8e5c4dc0 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:331 [inline]
 #0: ffffffff8e5c4dc0 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:841 [inline]
 #0: ffffffff8e5c4dc0 (rcu_read_lock){....}-{1:3}, at: debug_show_all_locks+0x36/0x1c0 kernel/locking/lockdep.c:6770
1 lock held by klogd/5192:
 #0: ffff8880b843a2d8 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested kernel/sched/core.c:614 [inline]
 #0: ffff8880b843a2d8 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x7e/0x130 kernel/sched/core.c:599
1 lock held by dhcpcd/5498:
 #0: ffffffff90362ea8 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_net_lock include/linux/rtnetlink.h:130 [inline]
 #0: ffffffff90362ea8 (rtnl_mutex){+.+.}-{4:4}, at: devinet_ioctl+0x26d/0x1f50 net/ipv4/devinet.c:1121
2 locks held by getty/5595:
 #0: ffff88814d8700a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x24/0x80 drivers/tty/tty_ldisc.c:243
 #1: ffffc9000333b2f0 (&ldata->atomic_read_lock){+.+.}-{4:4}, at: n_tty_read+0x41b/0x14f0 drivers/tty/n_tty.c:2222
2 locks held by syz.5.1147/10921:
 #0: ffff888059e21408 (&sb->s_type->i_mutex_key#11){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:869 [inline]
 #0: ffff888059e21408 (&sb->s_type->i_mutex_key#11){+.+.}-{4:4}, at: __sock_release+0x86/0x270 net/socket.c:646
 #1: ffffffff90362ea8 (rtnl_mutex){+.+.}-{4:4}, at: raw_release+0x1f3/0xbc0 net/can/raw.c:417
5 locks held by kworker/u8:20/10968:
 #0: ffff88801c6f3948 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work+0x12a2/0x1b70 kernel/workqueue.c:3213
 #1: ffffc9000b9afd10 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work+0x929/0x1b70 kernel/workqueue.c:3214
 #2: ffffffff9034ce50 (pernet_ops_rwsem){++++}-{4:4}, at: cleanup_net+0xad/0x890 net/core/net_namespace.c:662
 #3: ffffffff90362ea8 (rtnl_mutex){+.+.}-{4:4}, at: default_device_exit_batch+0x8b/0xaf0 net/core/dev.c:12630
 #4: ffffffff8e5d03b8 (rcu_state.exp_mutex){+.+.}-{4:4}, at: exp_funnel_lock+0x1a3/0x3c0 kernel/rcu/tree_exp.h:336
3 locks held by kworker/u8:28/10978:
 #0: ffff88801b881148 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x12a2/0x1b70 kernel/workqueue.c:3213
 #1: ffffc900040cfd10 ((linkwatch_work).work){+.+.}-{0:0}, at: process_one_work+0x929/0x1b70 kernel/workqueue.c:3214
 #2: ffffffff90362ea8 (rtnl_mutex){+.+.}-{4:4}, at: linkwatch_event+0x51/0xc0 net/core/link_watch.c:303
1 lock held by syz.4.1449/12799:
 #0: ffffffff8e5d03b8 (rcu_state.exp_mutex){+.+.}-{4:4}, at: exp_funnel_lock+0x1a3/0x3c0 kernel/rcu/tree_exp.h:336
1 lock held by syz.5.1447/12800:
 #0: ffffffff90362ea8 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_lock net/core/rtnetlink.c:80 [inline]
 #0: ffffffff90362ea8 (rtnl_mutex){+.+.}-{4:4}, at: rtnetlink_rcv_msg+0x371/0xe90 net/core/rtnetlink.c:6950
1 lock held by syz.3.1448/12802:
 #0: ffffffff90362ea8 (rtnl_mutex){+.+.}-{4:4}, at: tun_detach drivers/net/tun.c:633 [inline]
 #0: ffffffff90362ea8 (rtnl_mutex){+.+.}-{4:4}, at: tun_chr_close+0x38/0x230 drivers/net/tun.c:3396
1 lock held by syz.3.1448/12806:
 #0: ffffffff90362ea8 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_lock net/core/rtnetlink.c:80 [inline]
 #0: ffffffff90362ea8 (rtnl_mutex){+.+.}-{4:4}, at: rtnetlink_rcv_msg+0x371/0xe90 net/core/rtnetlink.c:6950

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

NMI backtrace for cpu 0
CPU: 0 UID: 0 PID: 31 Comm: khungtaskd Not tainted 6.16.0-rc5-syzkaller-00266-g3f31a806a62e #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120
 nmi_cpu_backtrace+0x27b/0x390 lib/nmi_backtrace.c:113
 nmi_trigger_cpumask_backtrace+0x29c/0x300 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:158 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:307 [inline]
 watchdog+0xf70/0x12c0 kernel/hung_task.c:470
 kthread+0x3c5/0x780 kernel/kthread.c:464
 ret_from_fork+0x5d7/0x6f0 arch/x86/kernel/process.c:148
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 UID: 0 PID: 12811 Comm: syz.0.1450 Not tainted 6.16.0-rc5-syzkaller-00266-g3f31a806a62e #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:lock_acquire+0x62/0x350 kernel/locking/lockdep.c:5875
Code: 45 38 12 83 f8 07 0f 87 bc 02 00 00 89 c0 48 0f a3 05 f2 fb 10 0f 0f 82 74 02 00 00 8b 35 da 2d 11 0f 85 f6 0f 85 8d 00 00 00 <48> 8b 44 24 30 65 48 2b 05 89 45 38 12 0f 85 c7 02 00 00 48 83 c4
RSP: 0018:ffffc90003cff5e0 EFLAGS: 00000206
RAX: 0000000000000046 RBX: ffffffff8e5c4dc0 RCX: 00000000ef9d33e4
RDX: 0000000000000000 RSI: ffffffff8de0d97d RDI: ffffffff8c158f60
RBP: 0000000000000002 R08: 0ac0d5affe09d4ff R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff888124813000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffc774ffc68 CR3: 0000000035f2f000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 rcu_lock_acquire include/linux/rcupdate.h:331 [inline]
 rcu_read_lock include/linux/rcupdate.h:841 [inline]
 class_rcu_constructor include/linux/rcupdate.h:1155 [inline]
 unwind_next_frame+0xd1/0x20a0 arch/x86/kernel/unwind_orc.c:479
 __unwind_start+0x45f/0x7f0 arch/x86/kernel/unwind_orc.c:758
 unwind_start arch/x86/include/asm/unwind.h:64 [inline]
 arch_stack_walk+0x73/0x100 arch/x86/kernel/stacktrace.c:24
 stack_trace_save+0x8e/0xc0 kernel/stacktrace.c:122
 save_stack+0x160/0x1f0 mm/page_owner.c:156
 __reset_page_owner+0x84/0x1a0 mm/page_owner.c:308
 reset_page_owner include/linux/page_owner.h:25 [inline]
 free_pages_prepare mm/page_alloc.c:1248 [inline]
 __free_frozen_pages+0x7fe/0x1180 mm/page_alloc.c:2706
 vfree+0x1fd/0xb50 mm/vmalloc.c:3434
 kcov_put kernel/kcov.c:439 [inline]
 kcov_put kernel/kcov.c:435 [inline]
 kcov_close+0x34/0x60 kernel/kcov.c:535
 __fput+0x3ff/0xb70 fs/file_table.c:465
 task_work_run+0x14d/0x240 kernel/task_work.c:227
 exit_task_work include/linux/task_work.h:40 [inline]
 do_exit+0x86c/0x2bd0 kernel/exit.c:964
 do_group_exit+0xd3/0x2a0 kernel/exit.c:1105
 get_signal+0x2673/0x26d0 kernel/signal.c:3034
 arch_do_signal_or_restart+0x8f/0x7d0 arch/x86/kernel/signal.c:337
 exit_to_user_mode_loop+0x84/0x110 kernel/entry/common.c:111
 exit_to_user_mode_prepare include/linux/entry-common.h:330 [inline]
 syscall_exit_to_user_mode_work include/linux/entry-common.h:414 [inline]
 syscall_exit_to_user_mode include/linux/entry-common.h:449 [inline]
 do_syscall_64+0x3f6/0x4c0 arch/x86/entry/syscall_64.c:100
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fe24238e929
Code: Unable to access opcode bytes at 0x7fe24238e8ff.
RSP: 002b:00007fe243135038 EFLAGS: 00000246 ORIG_RAX: 0000000000000133
RAX: 0000000000000001 RBX: 00007fe2425b6080 RCX: 00007fe24238e929
RDX: 0000000000000008 RSI: 0000200000004840 RDI: 0000000000000004
RBP: 00007fe242410b39 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000004000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007fe2425b6080 R15: 00007ffc9aff5518
 </TASK>

Crashes (421):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/07/13 12:23 upstream 3f31a806a62e 3cda49cf .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in hub_event
2025/07/11 14:25 upstream bc9ff192a6c9 3cda49cf .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2025/07/10 01:54 upstream 8c2e52ebbe88 f4e5e155 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2025/07/08 06:51 upstream d7b8f8e20813 4f67c4ae .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in hub_event
2025/07/07 12:20 upstream d7b8f8e20813 4f67c4ae .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in hub_event
2025/07/06 17:45 upstream 1f988d0788f5 4f67c4ae .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2025/07/05 05:31 upstream 4c06e63b9203 d869b261 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2025/07/03 18:00 upstream b4911fb0b060 115ceea7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2025/07/03 06:39 upstream b4911fb0b060 0cd59a8f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2025/07/02 21:15 upstream b4911fb0b060 0cd59a8f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2025/07/02 03:08 upstream 66701750d556 ffe4b334 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2025/07/01 03:25 upstream d0b3b7b22dfa 6e83b42d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in hub_event
2025/06/30 10:57 upstream d0b3b7b22dfa fc9d8ee5 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in hub_event
2025/06/29 19:38 upstream dfba48a70cb6 fc9d8ee5 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2025/06/26 16:52 upstream ee88bddf7f2f 26d77996 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2025/06/24 06:50 upstream 78f4e737a53e 1a7fb460 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2025/06/21 10:28 upstream 11313e2f7812 d6cdfb8a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in hub_event
2025/06/20 23:11 upstream 41687a5c6f8b e3003213 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in hub_event
2025/06/14 10:44 upstream 02adc1490e6d 0e8da31f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2025/06/11 12:41 upstream aef17cb3d3c4 5d7e17ca .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in hub_event
2025/06/09 13:21 upstream 19272b37aa4f 4826c28e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2025/06/07 01:20 upstream e271ed52b344 f61267d4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2025/06/05 23:31 upstream 7fdaba912981 6b6b5f21 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2025/06/03 23:39 upstream f5164456c604 a30356b7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in hub_event
2025/05/31 18:10 upstream 0f70f5b08a47 3d2f584d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2025/05/29 15:04 upstream 90b83efa6701 3d2f584d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in hub_event
2025/05/28 03:55 upstream 015a99fa7665 874a1386 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2025/05/25 04:50 upstream b1427432d3b6 ed351ea7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2025/05/24 10:25 upstream 4856ebd99715 ed351ea7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2025/05/23 06:45 upstream 94305e83eccb fa44301a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2025/05/17 01:50 upstream 3c21441eeffc f41472b0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in hub_event
2025/05/16 19:38 upstream 3c21441eeffc cfde8269 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in hub_event
2025/05/16 12:00 upstream fee3e843b309 cfde8269 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2025/05/13 05:07 upstream 82f2b0b97b36 f6671af7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2025/05/10 18:05 upstream 0e1329d4045c 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in hub_event
2025/05/03 19:38 upstream 95d3481af6dc b0714e37 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in hub_event
2025/05/03 15:51 upstream 95d3481af6dc b0714e37 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in hub_event
2025/05/03 03:06 upstream 2bfcee565c3a b0714e37 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in hub_event
2025/04/27 23:30 upstream 5bc1018675ec c6b4fb39 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in hub_event
2025/04/27 19:47 upstream 5bc1018675ec c6b4fb39 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in hub_event
2025/04/26 19:05 upstream f1a3944c860b c6b4fb39 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in hub_event
2025/04/26 16:19 upstream f1a3944c860b c6b4fb39 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in hub_event
2025/04/20 18:28 upstream 6fea5fabd332 2a20f901 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in hub_event
2025/04/20 13:39 upstream 119009db2674 2a20f901 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in hub_event
2025/07/09 21:43 upstream 733923397fd9 f4e5e155 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in hub_event
2023/01/14 13:26 upstream 97ec4d559d93 a63719e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2023/01/10 20:10 upstream 40c18f363a08 1dac8c7a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2022/12/31 00:37 upstream c8451c141e07 ab32d508 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2022/02/19 06:12 upstream 7993e65fdd0f 3cd800e4 .config console log report info ci-upstream-kasan-gce-root INFO: task hung in hub_event
2025/07/08 11:28 linux-next 58ba80c47402 4f67c4ae .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in hub_event
2025/07/08 02:51 linux-next 26ffb3d6f02c 4f67c4ae .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce INFO: task hung in hub_event
2025/07/02 07:19 linux-next 1343433ed389 ffe4b334 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in hub_event
2024/12/03 02:55 https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing e70140ba0d2b 578925bc .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-usb INFO: task hung in hub_event
2024/04/03 16:32 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 707081b61156 fed899ed .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in hub_event
* Struck through repros no longer work on HEAD.