syzbot
INFO: task hung in store_bind
Status:
upstream: reported on 2026/09/02 18:20
Reported-by: syzbot+b84c8a18033f6d57ee4e@syzkaller.appspotmail.com
First crash: 14d, last: 14d
Sample crash report:
INFO: task syz.0.1898:12315 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.1898 state:D stack:27432 pid:12315 ppid:5775 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5382 [inline]
__schedule+0x15ae/0x4660 kernel/sched/core.c:6701
schedule+0xbd/0x170 kernel/sched/core.c:6775
schedule_timeout+0xc1/0x2d0 kernel/time/timer.c:2144
___down_common kernel/locking/semaphore.c:229 [inline]
__down_common+0x30e/0x650 kernel/locking/semaphore.c:250
down+0x80/0xd0 kernel/locking/semaphore.c:64
console_lock+0x145/0x1b0 kernel/printk/printk.c:2686
store_bind+0x5d/0xa20 drivers/tty/vt/vt.c:3870
kernfs_fop_write_iter+0x3a4/0x520 fs/kernfs/file.c:352
call_write_iter include/linux/fs.h:2018 [inline]
new_sync_write fs/read_write.c:491 [inline]
vfs_write+0x474/0x9a0 fs/read_write.c:584
ksys_write+0x151/0x260 fs/read_write.c:637
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f2b82f9e159
RSP: 002b:00007f2b83eea028 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f2b83225fa0 RCX: 00007f2b82f9e159
RDX: 0000000000000001 RSI: 0000200000000280 RDI: 0000000000000003
RBP: 00007f2b83035024 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f2b83226038 R14: 00007f2b83225fa0 R15: 00007ffed1a812a8
</TASK>
Showing all locks held in the system:
1 lock held by khungtaskd/29:
#0: ffffffff8d1320e0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:334 [inline]
#0: ffffffff8d1320e0 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:786 [inline]
#0: ffffffff8d1320e0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x55/0x290 kernel/locking/lockdep.c:6633
2 locks held by getty/5532:
#0: ffff88802d1bc0a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
#1: ffffc9000327b2f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x428/0x1370 drivers/tty/n_tty.c:2217
4 locks held by kworker/0:7/6926:
3 locks held by kworker/u4:25/8422:
4 locks held by syz.0.1898/12315:
#0: ffff88802fdb2d48 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x2a3/0x330 fs/file.c:1040
#1: ffff88805734a418 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x21e/0x9a0 fs/read_write.c:580
#2: ffff88801dfb6488 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1dc/0x520 fs/kernfs/file.c:343
#3: ffff888141a4c8c0 (kn->active#85){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline]
#3: ffff888141a4c8c0 (kn->active#85){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x236/0x520 fs/kernfs/file.c:344
2 locks held by syz-executor/12499:
2 locks held by syz.7.2143/13231:
#0: ffffffff8d8b7388 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2044 [inline]
#0: ffffffff8d8b7388 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x211/0xcc0 drivers/tty/tty_io.c:2127
#1: ffff88807d5021c0 (&tty->legacy_mutex){+.+.}-{3:3}, at: tty_init_dev+0x74/0x4c0 drivers/tty/tty_io.c:1413
1 lock held by syz.4.2234/13511:
#0: ffffffff8d8b7388 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2044 [inline]
#0: ffffffff8d8b7388 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x211/0xcc0 drivers/tty/tty_io.c:2127
1 lock held by syz.6.2252/13559:
#0: ffffffff8d8b7388 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2044 [inline]
#0: ffffffff8d8b7388 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x211/0xcc0 drivers/tty/tty_io.c:2127
1 lock held by syz.9.2417/14099:
#0: ffffffff8d8b7388 (tty_mutex){+.+.}-{3:3}, at: ptmx_open+0xd0/0x2c0 drivers/tty/pty.c:823
1 lock held by syz.1.2421/14126:
#0: ffffffff8d8b7388 (tty_mutex){+.+.}-{3:3}, at: ptmx_open+0xd0/0x2c0 drivers/tty/pty.c:823
1 lock held by syz.0.2548/14627:
#0: ffffffff8d8b7388 (tty_mutex){+.+.}-{3:3}, at: ptmx_open+0xd0/0x2c0 drivers/tty/pty.c:823
1 lock held by syz-executor/14889:
1 lock held by dhcpcd-run-hook/14898:
#0: ffff88803ad21068 (&pipe->mutex/1){+.+.}-{3:3}, at: __pipe_lock fs/pipe.c:103 [inline]
#0: ffff88803ad21068 (&pipe->mutex/1){+.+.}-{3:3}, at: pipe_read+0xd81/0x1330 fs/pipe.c:382
2 locks held by syz.5.2630/14903:
1 lock held by dhcpcd-run-hook/14908:
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 29 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+0x18c/0x250 lib/dump_stack.c:106
nmi_cpu_backtrace+0x3a6/0x3e0 lib/nmi_backtrace.c:113
nmi_trigger_cpumask_backtrace+0x17a/0x2f0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:160 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:222 [inline]
watchdog+0xf59/0xfa0 kernel/hung_task.c:379
kthread+0x2fa/0x390 kernel/kthread.c:388
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
</TASK>
* Struck through repros no longer work on HEAD.