INFO: task hung in tty_release_struct

Status: upstream: reported on 2026/11/08 16:26
Reported-by: syzbot+2f9c42c0d4c4e47c8c06@syzkaller.appspotmail.com
First crash: 1h35m, last: 1h35m
▶ ▼ Similar bugs (13)
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 1423d 1423d 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 2383d 2493d 0/1 auto-closed as invalid on 2020/08/28 17:40
upstream INFO: task hung in tty_release_struct serial 1 2 2307d 2313d 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 80d 96d 0/29 upstream: reported on 2026/08/04 00:09
linux-6.6 INFO: task hung in tty_release_struct 1 2 53d 78d 0/2 upstream: reported on 2026/08/22 05:26
upstream INFO: task hung in tty_release_struct (6) serial 1 1 1028d 1028d 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 1741d 1877d 0/29 closed as invalid on 2022/02/07 19:19
upstream INFO: task hung in tty_release_struct (3) serial 1 3 1682d 1726d 0/29 auto-closed as invalid on 2022/06/29 20:46
android-414 INFO: task hung in tty_release_struct 1 7 2888d 2766d 0/1 auto-closed as invalid on 2019/06/10 11:00
upstream INFO: task hung in tty_release_struct (5) serial 1 1 1217d 1217d 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 737d 899d 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 1502d 1539d 0/29 auto-obsoleted due to no activity on 2023/01/03 08:49
linux-5.15 INFO: task hung in tty_release_struct 1 6 3d03h 94d 0/3 upstream: reported on 2026/08/06 00:13

Sample crash report:
INFO: task syz.2.2259:18291 blocked for more than 143 seconds.
      Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.2.2259      state:D stack:26256 pid:18291 ppid:4277   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_preempt_disabled+0xf/0x20 kernel/sched/core.c:6719
 __mutex_lock_common kernel/locking/mutex.c:679 [inline]
 __mutex_lock+0x562/0xb40 kernel/locking/mutex.c:747
 tty_release_struct+0xaa/0xd0 drivers/tty/tty_io.c:1701
 tty_release+0xbc5/0x14f0 drivers/tty/tty_io.c:1862
 __fput+0x20a/0x8b0 fs/file_table.c:320
 task_work_run+0x1d0/0x260 kernel/task_work.c:203
 resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
 exit_to_user_mode_loop+0xe6/0x110 kernel/entry/common.c:180
 exit_to_user_mode_prepare+0xee/0x180 kernel/entry/common.c:213
 __syscall_exit_to_user_mode_work kernel/entry/common.c:295 [inline]
 syscall_exit_to_user_mode+0x16/0x40 kernel/entry/common.c:306
 do_syscall_64+0x58/0xa0 arch/x86/entry/common.c:82
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f37a5b9fb19
RSP: 002b:00007ffdd5ad9638 EFLAGS: 00000246 ORIG_RAX: 00000000000001b4
RAX: 0000000000000000 RBX: 00007f37a5e27da0 RCX: 00007f37a5b9fb19
RDX: 0000000000000000 RSI: 000000000000001e RDI: 0000000000000003
RBP: 00007f37a5e27da0 R08: 0000000000000006 R09: 0000000000000000
R10: 00007f37a5e27cb0 R11: 0000000000000246 R12: 00000000000ecf6e
R13: 00007f37a5e2609c R14: 00000000000ecf3c R15: 00007f37a5e26090
 </TASK>

Showing all locks held in the system:
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
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
1 lock held by dhcpcd/3936:
 #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
2 locks held by getty/4032:
 #0: ffff888021b50098 (&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
3 locks held by kworker/0:4/9890:
 #0: ffff888018470938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
 #1: ffffc90003d37d00 ((work_completion)(&tn->work)){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
 #2: ffffffff8ed6b9e8 (rtnl_mutex){+.+.}-{3:3}, at: tipc_net_finalize_work+0x1a/0x90 net/tipc/net.c:148
3 locks held by kworker/0:3/17859:
 #0: ffff88803080e938 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
 #1: ffffc90003447d00 ((work_completion)(&(&ifa->dad_work)->work)){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
 #2: ffffffff8ed6b9e8 (rtnl_mutex){+.+.}-{3:3}, at: addrconf_dad_work+0xc4/0x1500 net/ipv6/addrconf.c:4146
2 locks held by kworker/0:11/17864:
 #0: ffff888144693d38 ((wq_completion)md_misc){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
 #1: ffffc900034ffd00 ((work_completion)(&mddev->del_work)#2){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
3 locks held by kworker/u4:0/17981:
 #0: ffff888018479138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
 #1: ffffc900032f7d00 ((linkwatch_work).work){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
 #2: ffffffff8ed6b9e8 (rtnl_mutex){+.+.}-{3:3}, at: linkwatch_event+0xa/0x50 net/core/link_watch.c:263
1 lock held by syz.2.2259/18291:
 #0: ffffffff8e2853e8 (tty_mutex){+.+.}-{3:3}, at: tty_release_struct+0xaa/0xd0 drivers/tty/tty_io.c:1701
3 locks held by syz.2.2259/18292:
1 lock held by syz.9.2294/19078:
 #0: ffffffff8e2853e8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2047 [inline]
 #0: ffffffff8e2853e8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x204/0xd80 drivers/tty/tty_io.c:2130
1 lock held by syz.0.2420/20209:
 #0: ffffffff8e2853e8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2047 [inline]
 #0: ffffffff8e2853e8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x204/0xd80 drivers/tty/tty_io.c:2130
1 lock held by syz.1.2427/20244:
 #0: ffffffff8e2853e8 (tty_mutex){+.+.}-{3:3}, at: ptmx_open+0xcc/0x2c0 drivers/tty/pty.c:823
1 lock held by syz-executor/21337:
 #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.6.2612/21998:
1 lock held by syz.5.2616/22043:
 #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.7.2622/22120:
 #0: ffffffff8ed6b9e8 (rtnl_mutex){+.+.}-{3:3}, at: raw_setsockopt+0xac5/0x1460 net/can/raw.c:572
1 lock held by syz.7.2622/22123:
 #0: ffffffff8ed6b9e8 (rtnl_mutex){+.+.}-{3:3}, at: isotp_bind+0x1b1/0x940 net/can/isotp.c:1521
1 lock held by syz.7.2622/22127:
 #0: ffffffff8ed6b9e8 (rtnl_mutex){+.+.}-{3:3}, at: isotp_bind+0x1b1/0x940 net/can/isotp.c:1521
1 lock held by syz.8.2624/22208:
 #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.8.2624/22211:
 #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 md4_resync/22526:

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

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/15/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>

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/11/08 16:25 linux-6.1.y c75b0cf0982c 5cecaf1f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in tty_release_struct
* Struck through repros no longer work on HEAD.