INFO: task hung in tty_release_struct

Status: upstream: reported on 2026/08/06 00:13
Reported-by: syzbot+b5d45664f813b26f41f1@syzkaller.appspotmail.com
First crash: 52d, last: 1d04h
▶ ▼ Similar bugs (12)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.19 INFO: task hung in tty_release_struct 1 1 1380d 1380d 0/1 auto-obsoleted due to no activity on 2023/04/15 07:55
linux-4.14 INFO: task hung in tty_release_struct 1 2 2340d 2450d 0/1 auto-closed as invalid on 2020/08/28 17:40
upstream INFO: task hung in tty_release_struct serial 1 2 2264d 2271d 0/29 auto-closed as invalid on 2020/10/13 06:21
upstream INFO: task hung in tty_release_struct (8) prio:high serial 1 33 37d 54d 0/29 upstream: reported on 2026/08/04 00:09
linux-6.6 INFO: task hung in tty_release_struct 1 2 10d 36d 0/2 upstream: reported on 2026/08/22 05:26
upstream INFO: task hung in tty_release_struct (6) serial 1 1 986d 986d 0/29 auto-obsoleted due to no activity on 2024/04/13 21:30
upstream INFO: task hung in tty_release_struct (2) serial 1 7 1698d 1834d 0/29 closed as invalid on 2022/02/07 19:19
upstream INFO: task hung in tty_release_struct (3) serial 1 3 1640d 1684d 0/29 auto-closed as invalid on 2022/06/29 20:46
android-414 INFO: task hung in tty_release_struct 1 7 2845d 2724d 0/1 auto-closed as invalid on 2019/06/10 11:00
upstream INFO: task hung in tty_release_struct (5) serial 1 1 1175d 1175d 0/29 auto-obsoleted due to no activity on 2023/10/07 22:46
upstream INFO: task hung in tty_release_struct (7) serial 1 5 694d 857d 0/29 auto-obsoleted due to no activity on 2025/01/30 06:07
upstream INFO: task hung in tty_release_struct (4) serial 1 2 1459d 1497d 0/29 auto-obsoleted due to no activity on 2023/01/03 08:49

Sample crash report:
INFO: task syz.7.1240:11893 blocked for more than 144 seconds.
      Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.7.1240      state:D stack:27536 pid:11893 ppid:  9946 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_preempt_disabled+0xf/0x20 kernel/sched/core.c:6537
 __mutex_lock_common+0xdf5/0x2400 kernel/locking/mutex.c:669
 __mutex_lock kernel/locking/mutex.c:729 [inline]
 mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
 tty_release_struct+0xaa/0xd0 drivers/tty/tty_io.c:1718
 tty_release+0xc29/0x1630 drivers/tty/tty_io.c:1880
 __fput+0x212/0x8c0 fs/file_table.c:311
 task_work_run+0x125/0x1a0 kernel/task_work.c:188
 tracehook_notify_resume include/linux/tracehook.h:189 [inline]
 exit_to_user_mode_loop+0x10f/0x130 kernel/entry/common.c:184
 exit_to_user_mode_prepare+0xee/0x180 kernel/entry/common.c:217
 __syscall_exit_to_user_mode_work kernel/entry/common.c:299 [inline]
 syscall_exit_to_user_mode+0x16/0x40 kernel/entry/common.c:310
 do_syscall_64+0x58/0xa0 arch/x86/entry/common.c:86
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7fb6202ce159
RSP: 002b:00007fff193d4a38 EFLAGS: 00000246 ORIG_RAX: 00000000000001b4
RAX: 0000000000000000 RBX: 00007fb620557da0 RCX: 00007fb6202ce159
RDX: 0000000000000000 RSI: 000000000000001e RDI: 0000000000000003
RBP: 00007fb620557da0 R08: 00007fb620556038 R09: 0000000000000000
R10: 00000000003ffd40 R11: 0000000000000246 R12: 00000000000ed914
R13: 00007fb620555fac R14: 00000000000ed63b R15: 00007fff193d4b40
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/27:
 #0: ffffffff8c31ef60 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
4 locks held by kworker/u4:4/1406:
2 locks held by getty/3945:
 #0: ffff88802c1e0098 (&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
3 locks held by kworker/u4:6/4269:
 #0: ffff888016c79138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x75c/0xff0 kernel/workqueue.c:-1
 #1: ffffc9000321fd00 ((linkwatch_work).work){+.+.}-{0:0}, at: process_one_work+0x79e/0xff0 kernel/workqueue.c:2285
 #2: ffffffff8d44d548 (rtnl_mutex){+.+.}-{3:3}, at: linkwatch_event+0xa/0x50 net/core/link_watch.c:251
1 lock held by md0_raid1/5543:
 #0: ffff88807ebf42c0 (&mddev->reconfig_mutex){+.+.}-{3:3}, at: mddev_trylock drivers/md/md.h:556 [inline]
 #0: ffff88807ebf42c0 (&mddev->reconfig_mutex){+.+.}-{3:3}, at: md_check_recovery+0x460/0x1280 drivers/md/md.c:9370
5 locks held by kworker/u4:10/6378:
3 locks held by kworker/0:10/6733:
3 locks held by kworker/u4:3/11352:
4 locks held by kworker/u4:5/11739:
1 lock held by syz.7.1240/11893:
 #0: ffffffff8c9f6768 (tty_mutex){+.+.}-{3:3}, at: tty_release_struct+0xaa/0xd0 drivers/tty/tty_io.c:1718
3 locks held by syz.1.1243/11922:
1 lock held by syz.0.1161/12132:
 #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.2.1262/12464:
 #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.3.1263/12733:
 #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.5.1292/12843:
 #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.1289/13058:
 #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.4.1302/13248:
 #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.8.1297/13253:
 #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.7.1309/13424:
 #0: ffffffff8c9f6768 (tty_mutex){+.+.}-{3:3}, at: ptmx_open+0xd2/0x2c0 drivers/tty/pty.c:823
1 lock held by syz.9.1312/13503:
 #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.0.1323/13760:
 #0: ffffffff8c9f6768 (tty_mutex){+.+.}-{3:3}, at: ptmx_open+0xd2/0x2c0 drivers/tty/pty.c:823
1 lock held by syz.2.1368/14407:
 #0: ffffffff8c9f6768 (tty_mutex){+.+.}-{3:3}, at: ptmx_open+0xd2/0x2c0 drivers/tty/pty.c:823
1 lock held by syz.6.1390/14620:
 #0: ffffffff8c9f6768 (tty_mutex){+.+.}-{3:3}, at: ptmx_open+0xd2/0x2c0 drivers/tty/pty.c:823
1 lock held by syz.1.1395/14657:
 #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.5.1402/14735:
 #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
2 locks held by syz-executor/14950:
1 lock held by syz-executor/14958:
 #0: ffffffff8d44d548 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:72 [inline]
 #0: ffffffff8d44d548 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x79f/0xf10 net/core/rtnetlink.c:5695
1 lock held by syz.8.1418/14962:
 #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

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

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>

Crashes (4):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/09/26 01:42 linux-5.15.y 0248c33e835e f281d9d2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in tty_release_struct
2026/09/04 11:24 linux-5.15.y 0996e0926f6b f65209a4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in tty_release_struct
2026/08/19 01:17 linux-5.15.y aabd761612db 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in tty_release_struct
2026/08/06 00:11 linux-5.15.y 6e2fd6534337 cd5b1963 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in tty_release_struct
* Struck through repros no longer work on HEAD.