syzbot
INFO: task hung in vcs_write
Status:
upstream: reported on 2026/11/04 12:29
Reported-by: syzbot+052289b8799d89d93a32@syzkaller.appspotmail.com
First crash: 9d00h, last: 9d00h
Sample crash report:
INFO: task syz.3.4:4422 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.3.4 state:D stack:27504 pid:4422 ppid:4275 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5257 [inline]
__schedule+0x1089/0x4140 kernel/sched/core.c:6584
schedule+0xb9/0x180 kernel/sched/core.c:6660
schedule_timeout+0xbd/0x2d0 kernel/time/timer.c:2144
___down_common kernel/locking/semaphore.c:229 [inline]
__down_common+0x321/0x7a0 kernel/locking/semaphore.c:250
down+0x7c/0xd0 kernel/locking/semaphore.c:64
console_lock+0x141/0x1c0 kernel/printk/printk.c:2629
vcs_write+0x142/0x1290 drivers/tty/vt/vc_screen.c:614
vfs_write+0x2dc/0x9a0 fs/read_write.c:582
ksys_write+0x14d/0x260 fs/read_write.c:637
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f4d0419fb19
RSP: 002b:00007f4d050be028 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f4d04426090 RCX: 00007f4d0419fb19
RDX: 0000000000001006 RSI: 00002000000019c0 RDI: 0000000000000003
RBP: 00007f4d04237b70 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f4d04426128 R14: 00007f4d04426090 R15: 00007ffc7b864898
</TASK>
Showing all locks held in the system:
2 locks held by kworker/0:0/7:
#0: ffff888018472138 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
#1: ffffc900000c7d00 ((work_completion)(&rew->rew_work)){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
1 lock held by rcu_tasks_kthre/12:
#0: ffffffff8db2e3f0 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x33/0xce0 kernel/rcu/tasks.h:543
1 lock held by rcu_tasks_trace/13:
#0: ffffffff8db2ec30 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x33/0xce0 kernel/rcu/tasks.h:543
7 locks held by kworker/0:1/14:
#0: ffff88814328d538 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
#1: ffffc90000137d00 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
#2: ffff888029bb8190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:885 [inline]
#2: ffff888029bb8190 (&dev->mutex){....}-{3:3}, at: hub_event+0x178/0x5200 drivers/usb/core/hub.c:5855
#3: ffff888029138190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:885 [inline]
#3: ffff888029138190 (&dev->mutex){....}-{3:3}, at: __device_attach+0x85/0x480 drivers/base/dd.c:1009
#4: ffff8880196fc118 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:885 [inline]
#4: ffff8880196fc118 (&dev->mutex){....}-{3:3}, at: __device_attach+0x85/0x480 drivers/base/dd.c:1009
#5: ffff8880589b02f0 (&dev->clientlist_mutex){+.+.}-{3:3}, at: drm_client_register+0x47/0x1f0 drivers/gpu/drm/drm_client.c:135
#6: ffffffff8e207b28 (registration_lock){+.+.}-{3:3}, at: register_framebuffer+0x2aa/0xc10 drivers/video/fbdev/core/fbmem.c:1732
1 lock held by khungtaskd/28:
#0: ffffffff8db2daa0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:350 [inline]
#0: ffffffff8db2daa0 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:791 [inline]
#0: ffffffff8db2daa0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x51/0x290 kernel/locking/lockdep.c:6669
3 locks held by kworker/0:3/3658:
2 locks held by getty/4028:
#0: ffff88814c908098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:244
#1: ffffc9000327b2f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x430/0x1400 drivers/tty/n_tty.c:2198
4 locks held by kworker/u4:7/4382:
#0: ffff88801861e938 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
#1: ffffc90004cf7d00 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
#2: ffffffff8ed5ead0 (pernet_ops_rwsem){++++}-{3:3}, at: cleanup_net+0x148/0xba0 net/core/net_namespace.c:594
#3: ffffffff8db337b8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:291 [inline]
#3: ffffffff8db337b8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x2ec/0x890 kernel/rcu/tree_exp.h:962
5 locks held by syz.3.4/4420:
4 locks held by udevd/4622:
#0: ffff88805afa7b08 (&p->lock){+.+.}-{3:3}, at: seq_read_iter+0x9d/0xc50 fs/seq_file.c:182
#1: ffff888030c87088 (&of->mutex){+.+.}-{3:3}, at: kernfs_seq_start+0x59/0x410 fs/kernfs/file.c:172
#2: ffff88807534b3a8 (kn->active#5){++++}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline]
#2: ffff88807534b3a8 (kn->active#5){++++}-{0:0}, at: kernfs_seq_start+0xae/0x410 fs/kernfs/file.c:173
#3: ffff888029138190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:885 [inline]
#3: ffff888029138190 (&dev->mutex){....}-{3:3}, at: uevent_show+0x16e/0x320 drivers/base/core.c:2670
1 lock held by syz.4.63/4654:
#0: ffffffff8e28cf28 (vc_sel.lock){+.+.}-{3:3}, at: set_selection_kernel+0x32/0x17a0 drivers/tty/vt/selection.c:358
3 locks held by kworker/0:21/5304:
#0: ffff888018470938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
#1: ffffc90003a97d00 ((work_completion)(&data->fib_event_work)){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
#2: ffff88802747e240 (&data->fib_lock){+.+.}-{3:3}, at: nsim_fib_event_work+0x283/0x3320 drivers/net/netdevsim/fib.c:1491
3 locks held by udevd/5476:
1 lock held by syz-executor/5528:
#0: ffffffff8ed6b9e8 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:74 [inline]
#0: ffffffff8ed6b9e8 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x80d/0xfb0 net/core/rtnetlink.c:6163
1 lock held by syz-executor/5623:
1 lock held by syz.2.231/5630:
#0: ffff8880799360e0 (&type->s_umount_key#67/1){+.+.}-{3:3}, at: alloc_super+0x1fb/0x930 fs/super.c:228
2 locks held by syz.4.238/5647:
2 locks held by syz.9.239/5648:
1 lock held by dhcpcd-run-hook/5654:
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 28 Comm: khungtaskd Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/07/2026
Call Trace:
<TASK>
dump_stack_lvl+0x188/0x24e lib/dump_stack.c:106
nmi_cpu_backtrace+0x3e6/0x460 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x1d4/0x450 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+0xf0e/0xf50 kernel/hung_task.c:377
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</TASK>
* Struck through repros no longer work on HEAD.