syzbot


INFO: task hung in hub_event (3)

Status: upstream: reported on 2023/01/14 20:19
Subsystems: usb
Labels: prio:high
[Documentation on labels]
Reported-by: syzbot+a7edecbf389d11a369d4@syzkaller.appspotmail.com
First crash: 1574d, last: 17h26m
✨ AI Jobs (2)
ID Workflow Result Correct Bug Created Started Finished Revision Error
0e6b0195-a08e-4d37-89ff-ee06e80bdfca assessment-security DenialOfService: ✅ Exploitable: ❌ FilesystemTrigger: ❌ NetworkTrigger: ❌ PeripheralTrigger: ✅ RemoteTrigger: ❌ Unprivileged: ❌ UserNamespace: ❌ VMGuestTrigger: ❌ VMHostTrigger: ✅ INFO: task hung in hub_event (3) 2026/05/21 01:58 2026/05/21 01:58 2026/05/21 02:26 cf874a1cf36318c06202027159ddac14acf00db7
790c0256-fbdb-4057-9028-f554675fc392 repro 💥 INFO: task hung in hub_event (3) 2026/03/10 12:21 2026/03/10 12:21 2026/03/10 12:21 5c03941b7fba0fd3b0326afc981322c89fe9ba52+ unexpected git log output: "warning: unable to access '/root/.config/git/attributes': Permission denied\nwarning: unable to access '/root/.config/git/attributes': Permission denied\n9197e5949a41cfb5d44a6b8a860766266340d558\nfirewire: ohci: initialize page array to use alloc_pages_bulk() correctly\no-takashi@sakamocchi.jp\nTakashi Sakamoto\nSat Feb 28 11:56:03 2026 +0900\n2f9339c052bdbafaa8b02188d069fbb0e8df1f26\nSat Feb 28 10:09:24 2026 -0800\nThe call of alloc_pages_bulk() skips to fill entries of page array when\nthe entries already have values. While, 1394 OHCI PCI driver passes the\npage array without initializing. It could cause invalid state at PFN\nvalidation in vmap().\n\nFixes: f2ae92780ab9 (\"firewire: ohci: split page allocation from dma mapping\")\nReported-by: John Ogness <john.ogness@linutronix.de>\nReported-and-tested-by: Harald Arnesen <linux@skogtun.org>\nReported-and-tested-by: David Gow <david@davidgow.net>\nCloses: https://lore.kernel.org/lkml/87tsv1vig5.fsf@jogness.linutronix.de/\nSigned-off-by: Takashi Sakamoto <o-takashi@sakamocchi.jp>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\n"
Discussions (11)
Title Replies (including bot) Last reply
[syzbot] Monthly usb report (Jun 2026) 0 (1) 2026/06/02 20:32
[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 (12)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in hub_event usb 1 19 2443d 2619d 0/29 auto-closed as invalid on 2020/01/02 20:34
linux-6.6 INFO: task hung in hub_event 1 1 228d 228d 0/2 auto-obsoleted due to no activity on 2026/02/04 22:05
linux-4.14 INFO: task hung in hub_event 1 5 1614d 1636d 0/1 auto-closed as invalid on 2022/05/10 10:19
linux-5.15 INFO: task hung in hub_event (4) 1 3 414d 428d 0/3 auto-obsoleted due to no activity on 2025/08/02 17:03
linux-6.1 INFO: task hung in hub_event (2) 1 1 996d 996d 0/3 auto-obsoleted due to no activity on 2023/12/29 05:51
linux-6.1 INFO: task hung in hub_event (4) 1 4 194d 228d 0/3 auto-obsoleted due to no activity on 2026/03/10 11:30
upstream INFO: task hung in hub_event (2) usb 1 27 1614d 1659d 0/29 closed as invalid on 2022/02/08 09:40
linux-5.15 INFO: task hung in hub_event (2) 1 1 902d 902d 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 431d 434d 0/3 auto-obsoleted due to no activity on 2025/07/16 18:44
linux-5.15 INFO: task hung in hub_event (3) 1 1 691d 691d 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 1014d 1177d 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 1159d 1188d 0/3 auto-obsoleted due to no activity on 2023/08/08 09:24

Sample crash report:
INFO: task kworker/1:11:6121 blocked for more than 143 seconds.
      Tainted: G             L      syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/1:11    state:D stack:21544 pid:6121  tgid:6121  ppid:2      task_flags:0x4208060 flags:0x00080000
Workqueue: usb_hub_wq hub_event
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5388 [inline]
 __schedule+0x1821/0x5740 kernel/sched/core.c:7189
 __schedule_loop kernel/sched/core.c:7268 [inline]
 schedule+0x164/0x360 kernel/sched/core.c:7283
 schedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:7340
 __mutex_lock_common kernel/locking/mutex.c:726 [inline]
 __mutex_lock+0x7f7/0x1550 kernel/locking/mutex.c:820
 hub_port_connect drivers/usb/core/hub.c:5465 [inline]
 hub_port_connect_change drivers/usb/core/hub.c:5707 [inline]
 port_event drivers/usb/core/hub.c:5871 [inline]
 hub_event+0x21a2/0x4f30 drivers/usb/core/hub.c:5953
 process_one_work kernel/workqueue.c:3314 [inline]
 process_scheduled_works+0xb5d/0x1860 kernel/workqueue.c:3397
 worker_thread+0xa53/0xfc0 kernel/workqueue.c:3478
 kthread+0x389/0x470 kernel/kthread.c:436
 ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/30:
 #0: ffffffff8e95cd20 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:300 [inline]
 #0: ffffffff8e95cd20 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:838 [inline]
 #0: ffffffff8e95cd20 (rcu_read_lock){....}-{1:3}, at: debug_show_all_locks+0x2e/0x180 kernel/locking/lockdep.c:6775
1 lock held by syslogd/4983:
 #0: ffff8880b873b0e0 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x31/0x150 kernel/sched/core.c:652
2 locks held by kworker/1:3/5367:
 #0: ffff88813fe43140 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3289 [inline]
 #0: ffff88813fe43140 ((wq_completion)events){+.+.}-{0:0}, at: process_scheduled_works+0xa35/0x1860 kernel/workqueue.c:3397
 #1: ffffc90003487c40 ((work_completion)(&fw_work->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3290 [inline]
 #1: ffffc90003487c40 ((work_completion)(&fw_work->work)){+.+.}-{0:0}, at: process_scheduled_works+0xa70/0x1860 kernel/workqueue.c:3397
2 locks held by getty/5392:
 #0: ffff888036a9e0a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: ffffc9000322b2e8 (&ldata->atomic_read_lock){+.+.}-{4:4}, at: n_tty_read+0x45c/0x13a0 drivers/tty/n_tty.c:2211
5 locks held by kworker/0:4/5726:
 #0: ffff888022282d40 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3289 [inline]
 #0: ffff888022282d40 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_scheduled_works+0xa35/0x1860 kernel/workqueue.c:3397
 #1: ffffc90004df7c40 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3290 [inline]
 #1: ffffc90004df7c40 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_scheduled_works+0xa70/0x1860 kernel/workqueue.c:3397
 #2: ffff88802ab0e1d8 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:1040 [inline]
 #2: ffff88802ab0e1d8 (&dev->mutex){....}-{4:4}, at: hub_event+0x17f/0x4f30 drivers/usb/core/hub.c:5899
 #3: ffff88802aaf3568 (&port_dev->status_lock){+.+.}-{4:4}, at: usb_lock_port drivers/usb/core/hub.c:3252 [inline]
 #3: ffff88802aaf3568 (&port_dev->status_lock){+.+.}-{4:4}, at: hub_port_connect drivers/usb/core/hub.c:5464 [inline]
 #3: ffff88802aaf3568 (&port_dev->status_lock){+.+.}-{4:4}, at: hub_port_connect_change drivers/usb/core/hub.c:5707 [inline]
 #3: ffff88802aaf3568 (&port_dev->status_lock){+.+.}-{4:4}, at: port_event drivers/usb/core/hub.c:5871 [inline]
 #3: ffff88802aaf3568 (&port_dev->status_lock){+.+.}-{4:4}, at: hub_event+0x217a/0x4f30 drivers/usb/core/hub.c:5953
 #4: ffff88802a792360 (hcd->address0_mutex){+.+.}-{4:4}, at: hub_port_connect drivers/usb/core/hub.c:5465 [inline]
 #4: ffff88802a792360 (hcd->address0_mutex){+.+.}-{4:4}, at: hub_port_connect_change drivers/usb/core/hub.c:5707 [inline]
 #4: ffff88802a792360 (hcd->address0_mutex){+.+.}-{4:4}, at: port_event drivers/usb/core/hub.c:5871 [inline]
 #4: ffff88802a792360 (hcd->address0_mutex){+.+.}-{4:4}, at: hub_event+0x21a2/0x4f30 drivers/usb/core/hub.c:5953
5 locks held by kworker/1:11/6121:
 #0: ffff888022282d40 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3289 [inline]
 #0: ffff888022282d40 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_scheduled_works+0xa35/0x1860 kernel/workqueue.c:3397
 #1: ffffc90005f9fc40 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3290 [inline]
 #1: ffffc90005f9fc40 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_scheduled_works+0xa70/0x1860 kernel/workqueue.c:3397
 #2: ffff88801f3d91d8 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:1040 [inline]
 #2: ffff88801f3d91d8 (&dev->mutex){....}-{4:4}, at: hub_event+0x17f/0x4f30 drivers/usb/core/hub.c:5899
 #3: ffff88801f3de568 (&port_dev->status_lock){+.+.}-{4:4}, at: usb_lock_port drivers/usb/core/hub.c:3252 [inline]
 #3: ffff88801f3de568 (&port_dev->status_lock){+.+.}-{4:4}, at: hub_port_connect drivers/usb/core/hub.c:5464 [inline]
 #3: ffff88801f3de568 (&port_dev->status_lock){+.+.}-{4:4}, at: hub_port_connect_change drivers/usb/core/hub.c:5707 [inline]
 #3: ffff88801f3de568 (&port_dev->status_lock){+.+.}-{4:4}, at: port_event drivers/usb/core/hub.c:5871 [inline]
 #3: ffff88801f3de568 (&port_dev->status_lock){+.+.}-{4:4}, at: hub_event+0x217a/0x4f30 drivers/usb/core/hub.c:5953
 #4: ffff88802c002260 (hcd->address0_mutex){+.+.}-{4:4}, at: hub_port_connect drivers/usb/core/hub.c:5465 [inline]
 #4: ffff88802c002260 (hcd->address0_mutex){+.+.}-{4:4}, at: hub_port_connect_change drivers/usb/core/hub.c:5707 [inline]
 #4: ffff88802c002260 (hcd->address0_mutex){+.+.}-{4:4}, at: port_event drivers/usb/core/hub.c:5871 [inline]
 #4: ffff88802c002260 (hcd->address0_mutex){+.+.}-{4:4}, at: hub_event+0x21a2/0x4f30 drivers/usb/core/hub.c:5953
5 locks held by kworker/0:14/6136:
 #0: ffff888022282d40 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3289 [inline]
 #0: ffff888022282d40 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_scheduled_works+0xa35/0x1860 kernel/workqueue.c:3397
 #1: ffffc900060afc40 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3290 [inline]
 #1: ffffc900060afc40 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_scheduled_works+0xa70/0x1860 kernel/workqueue.c:3397
 #2: ffff88802c1f01d8 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:1040 [inline]
 #2: ffff88802c1f01d8 (&dev->mutex){....}-{4:4}, at: hub_event+0x17f/0x4f30 drivers/usb/core/hub.c:5899
 #3: ffff88802c1f4568 (&port_dev->status_lock){+.+.}-{4:4}, at: usb_lock_port drivers/usb/core/hub.c:3252 [inline]
 #3: ffff88802c1f4568 (&port_dev->status_lock){+.+.}-{4:4}, at: hub_port_connect drivers/usb/core/hub.c:5464 [inline]
 #3: ffff88802c1f4568 (&port_dev->status_lock){+.+.}-{4:4}, at: hub_port_connect_change drivers/usb/core/hub.c:5707 [inline]
 #3: ffff88802c1f4568 (&port_dev->status_lock){+.+.}-{4:4}, at: port_event drivers/usb/core/hub.c:5871 [inline]
 #3: ffff88802c1f4568 (&port_dev->status_lock){+.+.}-{4:4}, at: hub_event+0x217a/0x4f30 drivers/usb/core/hub.c:5953
 #4: ffff88802c002260 (hcd->address0_mutex){+.+.}-{4:4}, at: hub_port_connect drivers/usb/core/hub.c:5465 [inline]
 #4: ffff88802c002260 (hcd->address0_mutex){+.+.}-{4:4}, at: hub_port_connect_change drivers/usb/core/hub.c:5707 [inline]
 #4: ffff88802c002260 (hcd->address0_mutex){+.+.}-{4:4}, at: port_event drivers/usb/core/hub.c:5871 [inline]
 #4: ffff88802c002260 (hcd->address0_mutex){+.+.}-{4:4}, at: hub_event+0x21a2/0x4f30 drivers/usb/core/hub.c:5953
3 locks held by kworker/1:2/11360:
 #0: ffff88813fe43140 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3289 [inline]
 #0: ffff88813fe43140 ((wq_completion)events){+.+.}-{0:0}, at: process_scheduled_works+0xa35/0x1860 kernel/workqueue.c:3397
 #1: ffffc900152ffc40 ((work_completion)(&fw_work->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3290 [inline]
 #1: ffffc900152ffc40 ((work_completion)(&fw_work->work)){+.+.}-{0:0}, at: process_scheduled_works+0xa70/0x1860 kernel/workqueue.c:3397
 #2: ffffffff8e7f9a68 (umhelper_sem){++++}-{4:4}, at: usermodehelper_read_lock_wait+0x10b/0x220 kernel/umh.c:246
1 lock held by syz.0.2057/13543:
 #0: ffffffff8e963028 (rcu_state.exp_mutex){+.+.}-{4:4}, at: exp_funnel_lock kernel/rcu/tree_exp.h:343 [inline]
 #0: ffffffff8e963028 (rcu_state.exp_mutex){+.+.}-{4:4}, at: synchronize_rcu_expedited+0x38d/0x770 kernel/rcu/tree_exp.h:961
2 locks held by syz.0.2057/13544:
2 locks held by dhcpcd/13555:
 #0: ffff888052ff0260 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1713 [inline]
 #0: ffff888052ff0260 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: packet_do_bind+0x33/0xe10 net/packet/af_packet.c:3204
 #1: ffffffff8e963028 (rcu_state.exp_mutex){+.+.}-{4:4}, at: exp_funnel_lock kernel/rcu/tree_exp.h:311 [inline]
 #1: ffffffff8e963028 (rcu_state.exp_mutex){+.+.}-{4:4}, at: synchronize_rcu_expedited+0x2d0/0x770 kernel/rcu/tree_exp.h:961

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

NMI backtrace for cpu 0
CPU: 0 UID: 0 PID: 30 Comm: khungtaskd Tainted: G             L      syzkaller #0 PREEMPT(full) 
Tainted: [L]=SOFTLOCKUP
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/09/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
 nmi_cpu_backtrace+0x274/0x2d0 lib/nmi_backtrace.c:113
 nmi_trigger_cpumask_backtrace+0x17a/0x300 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:162 [inline]
 __sys_info lib/sys_info.c:157 [inline]
 sys_info+0x135/0x170 lib/sys_info.c:165
 check_hung_uninterruptible_tasks kernel/hung_task.c:353 [inline]
 watchdog+0xfd3/0x1030 kernel/hung_task.c:561
 kthread+0x389/0x470 kernel/kthread.c:436
 ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158
 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: 13544 Comm: syz.0.2057 Tainted: G             L      syzkaller #0 PREEMPT(full) 
Tainted: [L]=SOFTLOCKUP
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/09/2026
RIP: 0010:wq_stack_extract io_uring/slist.h:78 [inline]
RIP: 0010:io_extract_req io_uring/io_uring.h:528 [inline]
RIP: 0010:__io_req_caches_free+0x75/0x270 io_uring/io_uring.c:2150
Code: 4c 89 64 24 08 41 bc 01 00 00 00 48 bd 91 10 00 00 00 00 ad de 4c 89 74 24 10 44 89 64 24 04 4c 89 f8 48 c1 e8 03 80 3c 18 00 <74> 08 4c 89 ff e8 31 28 06 01 4d 8b 27 41 80 7c 1d 00 00 74 08 4c
RSP: 0018:ffffc900001e7980 EFLAGS: 00000246
RAX: 1ffff11004c064af RBX: dffffc0000000000 RCX: 0000000000080000
RDX: ffffc90003dc9000 RSI: 0000000000052d08 RDI: 0000000000052d09
RBP: dead000000001091 R08: ffffffff903036f7 R09: 1ffffffff20606de
R10: dffffc0000000000 R11: fffffbfff20606df R12: 0000000000000278
R13: 1ffff110063b702b R14: ffff888031db8158 R15: ffff888026032578
FS:  00007f4ddf6146c0(0000) GS:ffff8881253a0000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ff6bda17dac CR3: 000000008e880000 CR4: 00000000003526f0
DR0: 0000000000000003 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 io_queue_deferred+0x81/0x3e0 io_uring/io_uring.c:461
 __io_submit_flush_completions+0xed6/0xff0 io_uring/io_uring.c:1172
 io_submit_flush_completions io_uring/io_uring.h:251 [inline]
 ctx_flush_and_put io_uring/tw.c:43 [inline]
 io_handle_tw_list+0x4d9/0x540 io_uring/tw.c:84
 tctx_task_work_run+0x55/0x300 io_uring/tw.c:132
 tctx_task_work+0x3f/0x90 io_uring/tw.c:150
 task_work_run+0x1d9/0x270 kernel/task_work.c:233
 get_signal+0x11eb/0x1330 kernel/signal.c:2810
 arch_do_signal_or_restart+0xbc/0x840 arch/x86/kernel/signal.c:337
 __exit_to_user_mode_loop kernel/entry/common.c:64 [inline]
 exit_to_user_mode_loop+0xa9/0x680 kernel/entry/common.c:98
 __exit_to_user_mode_prepare include/linux/irq-entry-common.h:207 [inline]
 syscall_exit_to_user_mode_prepare include/linux/irq-entry-common.h:230 [inline]
 syscall_exit_to_user_mode include/linux/entry-common.h:318 [inline]
 do_syscall_64+0x353/0x580 arch/x86/entry/syscall_64.c:100
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f4dde79ce59
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f4ddf614028 EFLAGS: 00000246 ORIG_RAX: 00000000000001aa
RAX: 0000000000001000 RBX: 00007f4ddea15fa0 RCX: 00007f4dde79ce59
RDX: 0000000000007721 RSI: 0000000000002219 RDI: 0000000000000000
RBP: 00007f4dde832d6f R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000016 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f4ddea16038 R14: 00007f4ddea15fa0 R15: 00007f4ddeb3fa48
 </TASK>

Crashes (873):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/06/12 11:01 upstream 2b414a95b8f7 e93da63e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2026/06/08 21:28 upstream 4549871118cf 656e94c6 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2026/06/07 21:39 upstream 33d8d8ec31b5 cc095639 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2026/06/07 10:08 upstream 979c294509f9 cc095639 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2026/06/04 13:02 upstream ba3e43a9e601 197909be .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2026/06/03 22:25 upstream ba3e43a9e601 234057e5 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2026/05/30 07:49 upstream 9215e74f228f 6b4a8443 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in hub_event
2026/05/25 09:22 upstream 6a97c4d5262d c69befb3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2026/05/15 13:32 upstream 70eda68668d1 9cd3beaa .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in hub_event
2026/05/13 15:58 upstream 1d5dcaa3bd65 fec2a7ee .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2026/05/07 16:00 upstream 5862221fdded f250db59 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2026/04/24 17:45 upstream dd6c438c3e64 1c2b9291 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in hub_event
2026/04/24 16:02 upstream dd6c438c3e64 1c2b9291 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in hub_event
2026/04/07 06:38 upstream bfe62a454542 4440e7c2 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in hub_event
2026/04/04 20:50 upstream 7ca6d1cfec80 4440e7c2 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2026/03/30 07:04 upstream f242ac4a0944 356bdfc9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in hub_event
2026/03/29 03:59 upstream be762d8b6dd7 356bdfc9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2026/03/28 15:51 upstream 7df48e363130 356bdfc9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in hub_event
2026/03/28 12:24 upstream 7df48e363130 356bdfc9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2026/03/26 12:28 upstream d2a43e7f89da c6143aac .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2026/03/24 10:50 upstream c369299895a5 baf8bf12 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2026/03/23 08:00 upstream 8d8bd2a5aa98 5b92003d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2026/03/23 01:11 upstream 8d8bd2a5aa98 5b92003d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2026/03/01 07:37 upstream 9197e5949a41 43249bac .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2026/02/26 11:25 upstream d9d32e5bd5a4 e0f78d93 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in hub_event
2026/02/24 11:15 upstream 7dff99b35460 41d2fa6a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2026/02/23 20:18 upstream 6de23f81a5e0 305c0ec5 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2026/02/16 13:27 upstream 26a4cfaff82a 1e62d198 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in hub_event
2026/02/16 05:12 upstream bb7a3fc2c976 1e62d198 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2025/10/28 07:27 upstream fd57572253bc fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root 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
2026/04/10 15:49 upstream 9a9c8ce300cd 38c8e246 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in hub_event
2026/04/04 22:17 upstream 7ca6d1cfec80 4440e7c2 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in hub_event
2026/03/16 15:51 upstream f338e7738378 64e21424 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in hub_event
2026/03/15 19:27 upstream 267594792a71 ee8d34d6 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in hub_event
2026/03/05 06:47 upstream ecc64d2dc9ff a9fe5c9e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in hub_event
2026/02/14 13:10 upstream 770aaedb461a 1e62d198 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in hub_event
2026/02/13 23:39 upstream cd7a5651db26 1e62d198 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in hub_event
2026/02/11 03:39 upstream dc855b77719f 441e25b7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in hub_event
2026/02/10 00:53 upstream 05f7e89ab973 4ab09a02 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in hub_event
2026/02/09 12:32 upstream 05f7e89ab973 df949cd9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in hub_event
2026/02/08 08:27 upstream e7aa57247700 4c131dc4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in hub_event
2026/02/07 19:10 upstream 2687c848e578 4c131dc4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in hub_event
2026/02/07 04:00 upstream 2687c848e578 f20fc9f9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in hub_event
2026/02/06 03:07 upstream 8fdb05de0e2d f03c4191 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in hub_event
2026/02/05 16:17 upstream f14faaf3a1fb 4936e85c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in hub_event
2026/02/03 13:08 upstream 6bd9ed02871f 6df4c87a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in hub_event
2026/02/02 10:19 upstream 18f7fcd5e69a 018ebef2 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in hub_event
2026/02/01 03:11 upstream ad9a728a3388 35764559 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in hub_event
2026/01/31 23:12 upstream ad9a728a3388 35764559 .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
2026/05/12 12:49 linux-next e98d21c170b0 d5b1a17d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce INFO: task hung in hub_event
2026/03/29 15:14 linux-next 3b058d1aeeef 356bdfc9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in hub_event
2026/02/07 09:39 https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing da87d45b1951 f20fc9f9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-usb INFO: task hung in hub_event
2026/05/18 14:33 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 5cbb61bf4168 55156e84 .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.