syzbot


INFO: task hung in hub_port_init

Status: upstream: reported C repro on 2023/03/11 21:39
Bug presence: origin:upstream
[Documentation on labels]
Reported-by: syzbot+4e99f9ce9d00f2c79090@syzkaller.appspotmail.com
First crash: 273d, last: 16h12m
Bug presence (1)
Date Name Commit Repro Result
2023/09/14 upstream (ToT) 9fdfb15a3dbf C [report] INFO: task hung in hub_port_init
Similar bugs (6)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in hub_port_init C done 15888 760d 1159d 22/25 fixed on 2021/11/10 00:50
linux-5.15 INFO: task hung in hub_port_init origin:upstream C error 38 3h37m 242d 0/3 upstream: reported C repro on 2023/04/11 08:33
upstream INFO: task hung in hub_port_init (3) usb C error 541 3d20h 256d 0/25 upstream: reported C repro on 2023/03/28 12:23
linux-4.14 INFO: task hung in hub_port_init C error 6032 399d 1162d 0/1 upstream: reported C repro on 2020/10/03 08:19
upstream INFO: task hung in hub_port_init (2) usb C error 486 291d 753d 24/25 fixed on 2023/02/24 13:50
linux-4.19 INFO: task hung in hub_port_init C 4279 284d 1162d 0/1 upstream: reported C repro on 2020/10/03 09:24
Fix bisection attempts (1)
Created Duration User Patch Repo Result
2023/11/25 23:23 1h53m bisect fix linux-6.1.y job log (0) log

Sample crash report:
INFO: task kworker/0:2:935 blocked for more than 143 seconds.
      Not tainted 6.1.53-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/0:2     state:D stack:25056 pid:935   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
 usb_kill_urb+0x1c5/0x300 drivers/usb/core/urb.c:728
 usb_start_wait_urb+0x1ac/0x510 drivers/usb/core/message.c:64
 usb_internal_control_msg drivers/usb/core/message.c:102 [inline]
 usb_control_msg+0x2ad/0x4c0 drivers/usb/core/message.c:153
 get_bMaxPacketSize0 drivers/usb/core/hub.c:4697 [inline]
 hub_port_init+0x1190/0x27e0 drivers/usb/core/hub.c:4965
 hub_port_connect drivers/usb/core/hub.c:5344 [inline]
 hub_port_connect_change drivers/usb/core/hub.c:5555 [inline]
 port_event drivers/usb/core/hub.c:5711 [inline]
 hub_event+0x2b31/0x5710 drivers/usb/core/hub.c:5793
 process_one_work+0x8aa/0x11f0 kernel/workqueue.c:2292
 worker_thread+0xa5f/0x1210 kernel/workqueue.c:2439
 kthread+0x26e/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: ffffffff8d12a1b0 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xd20 kernel/rcu/tasks.h:516
1 lock held by rcu_tasks_trace/13:
 #0: ffffffff8d12a9b0 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xd20 kernel/rcu/tasks.h:516
1 lock held by khungtaskd/28:
 #0: ffffffff8d129fe0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
5 locks held by kworker/0:2/935:
 #0: ffff88801827a538 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x77a/0x11f0
 #1: ffffc900049c7d20 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x7bd/0x11f0 kernel/workqueue.c:2267
 #2: ffff888145709190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:836 [inline]
 #2: ffff888145709190 (&dev->mutex){....}-{3:3}, at: hub_event+0x1fe/0x5710 drivers/usb/core/hub.c:5739
 #3: ffff88814570c4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: usb_lock_port drivers/usb/core/hub.c:3110 [inline]
 #3: ffff88814570c4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_port_connect drivers/usb/core/hub.c:5311 [inline]
 #3: ffff88814570c4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_port_connect_change drivers/usb/core/hub.c:5555 [inline]
 #3: ffff88814570c4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: port_event drivers/usb/core/hub.c:5711 [inline]
 #3: ffff88814570c4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_event+0x2471/0x5710 drivers/usb/core/hub.c:5793
 #4: ffff88814536d168 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_port_connect drivers/usb/core/hub.c:5312 [inline]
 #4: ffff88814536d168 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_port_connect_change drivers/usb/core/hub.c:5555 [inline]
 #4: ffff88814536d168 (hcd->address0_mutex){+.+.}-{3:3}, at: port_event drivers/usb/core/hub.c:5711 [inline]
 #4: ffff88814536d168 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_event+0x249e/0x5710 drivers/usb/core/hub.c:5793
2 locks held by getty/3310:
 #0: ffff888028c37098 (&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:2188

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

NMI backtrace for cpu 0
CPU: 0 PID: 28 Comm: khungtaskd Not tainted 6.1.53-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/04/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+0x26e/0x300 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
 </TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 98 Comm: kworker/u4:4 Not tainted 6.1.53-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/04/2023
Workqueue: events_unbound toggle_allocation_gate
RIP: 0010:insn_get_immediate+0x5c/0x1390 arch/x86/lib/insn.c:631
Code: c0 0f 85 05 0d 00 00 41 0f b6 5d 00 31 ed 31 ff 89 de e8 37 53 06 f7 85 db 74 0a e8 ce 50 06 f7 e9 76 0c 00 00 49 8d 6c 24 34 <48> 89 e8 48 c1 e8 03 42 0f b6 04 38 84 c0 0f 85 34 0d 00 00 0f b6
RSP: 0018:ffffc900015c7880 EFLAGS: 00000246
RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffff888013f75940
RDX: ffff888013f75940 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc900015c79b4 R08: ffffffff8a83c359 R09: ffffc900015c7980
R10: 0000000000000000 R11: dffffc0000000001 R12: ffffc900015c7980
R13: ffffc900015c79bc R14: 1ffff920002b8f37 R15: dffffc0000000000
FS:  0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000563c9e8b0768 CR3: 000000000ce8e000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <NMI>
 </NMI>
 <TASK>
 insn_get_length arch/x86/lib/insn.c:707 [inline]
 insn_decode+0x36c/0x500 arch/x86/lib/insn.c:747
 text_poke_loc_init+0xd2/0x680 arch/x86/kernel/alternative.c:1620
 arch_jump_label_transform_queue+0x71/0xd0 arch/x86/kernel/jump_label.c:138
 __jump_label_update+0x177/0x3a0 kernel/jump_label.c:447
 static_key_disable_cpuslocked+0xca/0x1b0 kernel/jump_label.c:207
 static_key_disable+0x16/0x20 kernel/jump_label.c:215
 toggle_allocation_gate+0x3e0/0x480 mm/kfence/core.c:818
 process_one_work+0x8aa/0x11f0 kernel/workqueue.c:2292
 worker_thread+0xa5f/0x1210 kernel/workqueue.c:2439
 kthread+0x26e/0x300 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
 </TASK>
INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to run: 1.319 msecs

Crashes (37):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/09/14 12:37 linux-6.1.y 09045dae0d90 0b6a67ac .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in hub_port_init
2023/06/11 02:26 linux-6.1.y 2f3918bc53fb 49519f06 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in hub_port_init
2023/08/16 14:24 linux-6.1.y 1321ab403b38 39990d51 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in hub_port_init
2023/08/15 23:45 linux-6.1.y 1321ab403b38 39990d51 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in hub_port_init
2023/11/27 12:14 linux-6.1.y 69e434a1cb21 5b429f39 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in hub_port_init
2023/11/26 09:43 linux-6.1.y 69e434a1cb21 5b429f39 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in hub_port_init
2023/09/19 20:59 linux-6.1.y a356197db198 0b6a67ac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in hub_port_init
2023/12/09 09:58 linux-6.1.y 6c6a6c7e211c 28b24332 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in hub_port_init
2023/10/23 22:28 linux-6.1.y 7d24402875c7 989a3687 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in hub_port_init
2023/09/25 19:45 linux-6.1.y d23900f974e0 0b6a67ac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in hub_port_init
2023/06/23 04:02 linux-6.1.y e84a4e368abe 79782afc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in hub_port_init
2023/06/17 08:03 linux-6.1.y ca87e77a2ef8 f3921d4d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in hub_port_init
2023/06/05 18:48 linux-6.1.y 76ba310227d2 a4ae4f42 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in hub_port_init
2023/06/02 08:03 linux-6.1.y d2869ace6eeb a4ae4f42 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in hub_port_init
2023/06/01 11:24 linux-6.1.y d2869ace6eeb babc4389 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in hub_port_init
2023/05/31 03:04 linux-6.1.y d2869ace6eeb df37c7f1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in hub_port_init
2023/05/26 19:31 linux-6.1.y a343b0dd87b4 cf184559 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in hub_port_init
2023/05/26 18:53 linux-6.1.y a343b0dd87b4 cf184559 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in hub_port_init
2023/05/26 16:42 linux-6.1.y a343b0dd87b4 b40ef614 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in hub_port_init
2023/05/26 08:11 linux-6.1.y a343b0dd87b4 b40ef614 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in hub_port_init
2023/05/25 16:38 linux-6.1.y a343b0dd87b4 0513b3e6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in hub_port_init
2023/05/21 00:45 linux-6.1.y fa74641fb6b9 4bce1a3e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in hub_port_init
2023/04/16 09:30 linux-6.1.y 0102425ac76b ec410564 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in hub_port_init
2023/04/14 06:04 linux-6.1.y 0102425ac76b 3cfcaa1b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in hub_port_init
2023/03/27 17:51 linux-6.1.y e3a87a10f259 f8f96aa9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in hub_port_init
2023/07/16 00:22 linux-6.1.y 61fd484b2cf6 35d9ecc5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in hub_port_init
2023/07/02 01:27 linux-6.1.y 0f4ac6b4c5f0 bfc47836 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in hub_port_init
2023/06/30 23:45 linux-6.1.y a1c449d00ff8 af3053d2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in hub_port_init
2023/06/25 05:42 linux-6.1.y e84a4e368abe 79782afc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in hub_port_init
2023/06/23 18:08 linux-6.1.y e84a4e368abe 79782afc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in hub_port_init
2023/06/23 01:39 linux-6.1.y e84a4e368abe 79782afc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in hub_port_init
2023/06/11 21:49 linux-6.1.y 2f3918bc53fb 49519f06 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in hub_port_init
2023/05/18 21:11 linux-6.1.y fa74641fb6b9 3bb7af1d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in hub_port_init
2023/04/23 16:21 linux-6.1.y f17b0ab65d17 2b32bd34 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in hub_port_init
2023/04/16 22:25 linux-6.1.y 0102425ac76b ec410564 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in hub_port_init
2023/04/05 11:21 linux-6.1.y 3b29299e5f60 831373d3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in hub_port_init
2023/03/11 21:39 linux-6.1.y 11585e2f8b9d 5205ef30 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in hub_port_init
* Struck through repros no longer work on HEAD.