syzbot
INFO: task hung in vcs_open
Status:
upstream: reported on 2026/08/03 15:31
Reported-by: syzbot+0b26cf09ae715791b68d@syzkaller.appspotmail.com
First crash: 28d, last: 4d21h
Sample crash report:
INFO: task syz.0.739:6422 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.0.739 state:D stack:25968 pid: 6422 ppid: 4190 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
vcs_open+0x59/0xc0 drivers/tty/vt/vc_screen.c:763
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:0x7f873fb3b0d9
RSP: 002b:00007f873dd93028 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007f873fdc2fa0 RCX: 00007f873fb3b0d9
RDX: 0000000000145042 RSI: 0000200000000d80 RDI: ffffffffffffff9c
RBP: 00007f873fbd2024 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000000001ca R11: 0000000000000246 R12: 0000000000000000
R13: 00007f873fdc3038 R14: 00007f873fdc2fa0 R15: 00007ffee09815d8
</TASK>
Showing all locks held in the system:
5 locks held by kworker/0:0/7:
#0: ffff8881419d6938 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x75c/0xff0 kernel/workqueue.c:-1
#1: ffffc90000cc7d00 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x79e/0xff0 kernel/workqueue.c:2285
#2: ffff888024583220 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:809 [inline]
#2: ffff888024583220 (&dev->mutex){....}-{3:3}, at: hub_event+0x178/0x5260 drivers/usb/core/hub.c:5827
#3: ffff8881419a7220 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:809 [inline]
#3: ffff8881419a7220 (&dev->mutex){....}-{3:3}, at: __device_attach+0x85/0x480 drivers/base/dd.c:974
#4: ffff888078c441a8 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:809 [inline]
#4: ffff888078c441a8 (&dev->mutex){....}-{3:3}, at: __device_attach+0x85/0x480 drivers/base/dd.c:974
3 locks held by kworker/u4:0/9:
#0: ffff888016dcd938 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work+0x75c/0xff0 kernel/workqueue.c:-1
#1: ffffc90000ce7d00 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work+0x79e/0xff0 kernel/workqueue.c:2285
#2: ffffffff8d440cd0 (pernet_ops_rwsem){++++}-{3:3}, at: cleanup_net+0x148/0xba0 net/core/net_namespace.c:589
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:4/1229:
#0: ffff888016c79138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x75c/0xff0 kernel/workqueue.c:-1
#1: ffffc90005307d00 ((reaper_work).work){+.+.}-{0:0}, at: process_one_work+0x79e/0xff0 kernel/workqueue.c:2285
1 lock held by klogd/3547:
1 lock held by udevd/3558:
2 locks held by getty/3944:
#0: ffff88814cb76098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffffc90002cf62e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x594/0x1a50 drivers/tty/n_tty.c:2158
2 locks held by kworker/u4:5/4236:
4 locks held by udevd/4259:
#0: ffff88804ce4fe80 (&p->lock){+.+.}-{3:3}, at: seq_read_iter+0x9d/0xc50 fs/seq_file.c:182
#1: ffff888059fc1088 (&of->mutex){+.+.}-{3:3}, at: kernfs_seq_start+0x55/0x3c0 fs/kernfs/file.c:112
#2: ffff88804ab04748 (kn->active#32){++++}-{0:0}, at: kernfs_seq_start+0x75/0x3c0 fs/kernfs/file.c:113
#3: ffff8881419a7220 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:809 [inline]
#3: ffff8881419a7220 (&dev->mutex){....}-{3:3}, at: uevent_show+0x16c/0x320 drivers/base/core.c:2408
2 locks held by udevd/4264:
5 locks held by syz.3.594/5838:
2 locks held by syz-executor/5862:
4 locks held by syz.1.909/6995:
#0: ffff888060843098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffff888016de00b8 (&buf->lock){+.+.}-{3:3}, at: tiocsti+0x192/0x270 drivers/tty/tty_io.c:2310
#2: ffff8880608432e8 (&tty->termios_rwsem){++++}-{3:3}, at: n_tty_receive_buf_common+0x87/0x65b0 drivers/tty/n_tty.c:1637
#3: ffffc900012cc378 (&ldata->output_lock){+.+.}-{3:3}, at: commit_echoes drivers/tty/n_tty.c:775 [inline]
#3: ffffc900012cc378 (&ldata->output_lock){+.+.}-{3:3}, at: n_tty_receive_char+0x5ed/0xbb0 drivers/tty/n_tty.c:1411
2 locks held by syz.1.909/6996:
#0: ffff888060843098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffff888016de00b8 (&buf->lock){+.+.}-{3:3}, at: tiocsti+0x192/0x270 drivers/tty/tty_io.c:2310
2 locks held by syz.1.909/6999:
#0: ffff888060843098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffff888016de00b8 (&buf->lock){+.+.}-{3:3}, at: tiocsti+0x192/0x270 drivers/tty/tty_io.c:2310
4 locks held by syz.6.1048/7386:
#0: ffff88802c99a370 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x2bf/0x370 fs/file.c:1056
#1: ffff88801fb44460 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x296/0xd70 fs/read_write.c:590
#2: ffff88801b9ec888 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1dc/0x500 fs/kernfs/file.c:287
#3: ffff88801b7f3748 (kn->active#805){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x1fd/0x500 fs/kernfs/file.c:288
3 locks held by kworker/0:21/7527:
2 locks held by syz-executor/7783:
2 locks held by kworker/u4:9/7800:
#0: ffff888016c79138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x75c/0xff0 kernel/workqueue.c:-1
#1: ffffc9000475fd00 (connector_reaper_work){+.+.}-{0:0}, at: process_one_work+0x79e/0xff0 kernel/workqueue.c:2285
1 lock held by syz.4.1199/7846:
2 locks held by v4l_id/7868:
=============================================
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.