syzbot
INFO: task hung in con_install
Status:
upstream: reported on 2026/07/25 09:43
Reported-by: syzbot+e606af51f0c2a8f3978c@syzkaller.appspotmail.com
First crash: 59d, last: 6d19h
Sample crash report:
INFO: task syz.4.646:7285 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.4.646 state:D stack:25520 pid: 7285 ppid: 4199 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5049 [inline]
__schedule+0x11c3/0x4350 kernel/sched/core.c:6395
schedule+0x11b/0x1e0 kernel/sched/core.c:6478
schedule_timeout+0xbd/0x2d0 kernel/time/timer.c:2093
__down_common+0x289/0x3b0 kernel/locking/semaphore.c:228
down+0x7e/0xd0 kernel/locking/semaphore.c:63
console_lock+0x29/0x70 kernel/printk/printk.c:2557
con_install+0x94/0x720 drivers/tty/vt/vt.c:3381
tty_driver_install_tty drivers/tty/tty_io.c:1317 [inline]
tty_init_dev+0xbb/0x470 drivers/tty/tty_io.c:1431
tty_open_by_driver drivers/tty/tty_io.c:2100 [inline]
tty_open+0x7e8/0xcd0 drivers/tty/tty_io.c:2148
chrdev_open+0x585/0x5f0 fs/char_dev.c:414
do_dentry_open+0x7f7/0xf90 fs/open.c:826
do_open fs/namei.c:3659 [inline]
path_openat+0x2718/0x2fb0 fs/namei.c:3793
do_filp_open+0x1df/0x400 fs/namei.c:3820
do_sys_openat2+0x14b/0x500 fs/open.c:1255
do_sys_open fs/open.c:1271 [inline]
__do_sys_openat fs/open.c:1287 [inline]
__se_sys_openat fs/open.c:1282 [inline]
__x64_sys_openat+0x135/0x160 fs/open.c:1282
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f470c83598e
RSP: 002b:00007f470aaccb28 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007f470aacd6c0 RCX: 00007f470c83598e
RDX: 0000000000000002 RSI: 00007f470aaccc00 RDI: ffffffffffffff9c
RBP: 00007f470c90c06b R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f470cafd038 R14: 00007f470cafcfa0 R15: 00007ffe840da688
</TASK>
Showing all locks held in the system:
3 locks held by kworker/0:0/7:
1 lock held by khungtaskd/27:
#0: ffffffff8c31ef60 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by kworker/u4:3/1172:
#0: ffff888016c79138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x75c/0xff0 kernel/workqueue.c:-1
#1: ffffc90004ba7d00 ((work_completion)(&sub_info->work)){+.+.}-{0:0}, at: process_one_work+0x79e/0xff0 kernel/workqueue.c:2285
2 locks held by kworker/0:1H/1236:
2 locks held by getty/3943:
#0: ffff88802c7f6098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffffc900021ce2e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x594/0x1a50 drivers/tty/n_tty.c:2158
2 locks held by kworker/u4:16/5670:
#0: ffff888016c79138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x75c/0xff0 kernel/workqueue.c:-1
#1: ffffc900023d7d00 (connector_reaper_work){+.+.}-{0:0}, at: process_one_work+0x79e/0xff0 kernel/workqueue.c:2285
2 locks held by kworker/u4:19/5674:
2 locks held by kworker/u4:20/5675:
#0: ffff888016c79138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x75c/0xff0 kernel/workqueue.c:-1
#1: ffffc900032bfd00 ((reaper_work).work){+.+.}-{0:0}, at: process_one_work+0x79e/0xff0 kernel/workqueue.c:2285
5 locks held by syz.0.607/7106:
2 locks held by syz.4.646/7285:
#0: ffffffff8c9f6768 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2064 [inline]
#0: ffffffff8c9f6768 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x20a/0xcd0 drivers/tty/tty_io.c:2148
#1: ffff8880756d61c0 (&tty->legacy_mutex){+.+.}-{3:3}, at: tty_init_dev+0x6f/0x470 drivers/tty/tty_io.c:1430
1 lock held by syz.2.681/7480:
#0: ffffffff8c9f6768 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2064 [inline]
#0: ffffffff8c9f6768 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x20a/0xcd0 drivers/tty/tty_io.c:2148
1 lock held by syz.6.741/7815:
#0: ffffffff8c9f6768 (tty_mutex){+.+.}-{3:3}, at: ptmx_open+0xd2/0x2c0 drivers/tty/pty.c:823
3 locks held by syz.7.811/8148:
#0: ffff888022b7b270 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x2bf/0x370 fs/file.c:1056
#1: ffff88801f8952f0 (&p->lock){+.+.}-{3:3}, at: seq_read_iter+0x9d/0xc50 fs/seq_file.c:182
#2: ffffffff8c9f6768 (tty_mutex){+.+.}-{3:3}, at: t_start+0x17/0x50 fs/proc/proc_tty.c:108
1 lock held by syz.3.887/8507:
2 locks held by modprobe/8521:
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 27 Comm: khungtaskd Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Call Trace:
<TASK>
dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106
nmi_cpu_backtrace+0x3a2/0x3d0 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x163/0x280 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:212 [inline]
watchdog+0xe1b/0xe60 kernel/hung_task.c:369
kthread+0x42e/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
* Struck through repros no longer work on HEAD.