INFO: task hung in tty_open

Status: upstream: reported on 2026/08/03 13:33
Reported-by: syzbot+7079ad18402f43113752@syzkaller.appspotmail.com
First crash: 106d, last: 3d19h
▶ ▼ Similar bugs (11)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 INFO: task hung in tty_open 1 22 6h26m 105d 0/3 upstream: reported on 2026/08/04 17:29
upstream INFO: task hung in tty_open serial 1 1 1870d 1870d 0/29 auto-closed as invalid on 2022/01/02 10:09
linux-4.14 INFO: task hung in tty_open (2) 1 1 1404d 1404d 0/1 upstream: reported on 2023/01/13 14:16
android-44 INFO: task hung in tty_open 1 syz, C 132 2559d 2775d 0/2 public: reported C repro on 2019/04/13 00:00
linux-6.6 INFO: task hung in tty_open 1 2 66d 109d 0/2 upstream: reported on 2026/07/31 15:41
upstream INFO: task hung in tty_open (2) serial 1 syz, C error error 19 1209d 1744d 0/29 auto-obsoleted due to no activity on 2023/11/04 13:34
linux-4.14 INFO: task hung in tty_open 1 2 2311d 2363d 0/1 auto-closed as invalid on 2020/11/17 06:29
android-414 INFO: task hung in tty_open 1 syz, C 152 2755d 2777d 0/1 public: reported C repro on 2019/04/11 00:00
upstream INFO: task can't die in show_free_areas serial prio:low 1 syz, C error error 305 24d 1758d 0/29 upstream: reported C repro on 2022/01/24 13:23
android-49 INFO: task hung in tty_open 1 syz, C 447 2540d 2776d 0/3 public: reported C repro on 2019/04/12 00:00
upstream INFO: task can't die in irqentry_exit (2) kernel 1 syz, C error 22 1749d 2165d 0/29 auto-obsoleted due to no activity on 2022/10/23 05:49

Sample crash report:
INFO: task syz.3.1350:11847 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.1350      state:D stack:24560 pid:11847 ppid:11551  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_open_by_driver drivers/tty/tty_io.c:2047 [inline]
 tty_open+0x204/0xd80 drivers/tty/tty_io.c:2130
 chrdev_open+0x585/0x5f0 fs/char_dev.c:414
 do_dentry_open+0x7dd/0x10b0 fs/open.c:882
 do_open fs/namei.c:3677 [inline]
 path_openat+0x2674/0x2f10 fs/namei.c:3838
 do_filp_open+0x1ee/0x420 fs/namei.c:3865
 do_sys_openat2+0x14b/0x4f0 fs/open.c:1320
 do_sys_open fs/open.c:1336 [inline]
 __do_sys_openat fs/open.c:1352 [inline]
 __se_sys_openat fs/open.c:1347 [inline]
 __x64_sys_openat+0x135/0x160 fs/open.c:1347
 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:0x7f4c32d69d0e
RSP: 002b:00007f4c33c94b28 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007f4c33c956c0 RCX: 00007f4c32d69d0e
RDX: 0000000000000002 RSI: 00007f4c33c94c00 RDI: ffffffffffffff9c
RBP: 00007f4c32e3804e R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f4c33026128 R14: 00007f4c33026090 R15: 00007ffc12a81c68
 </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/27:
 #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:2/129:
 #0: ffff888018470938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
 #1: ffffc90002e07d00 ((work_completion)(&data->fib_event_work)){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
 #2: ffff888039fd0240 (&data->fib_lock){+.+.}-{3:3}, at: nsim_fib_event_work+0x283/0x3320 drivers/net/netdevsim/fib.c:1491
2 locks held by getty/4034:
 #0: ffff88814ce23098 (&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
6 locks held by kworker/0:3/4348:
 #0: ffff8881436bc538 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
 #1: ffffc90004587d00 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
 #2: ffff888145bee190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:885 [inline]
 #2: ffff888145bee190 (&dev->mutex){....}-{3:3}, at: hub_event+0x178/0x5200 drivers/usb/core/hub.c:5855
 #3: ffff888055188190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:885 [inline]
 #3: ffff888055188190 (&dev->mutex){....}-{3:3}, at: __device_attach+0x85/0x480 drivers/base/dd.c:1009
 #4: ffff8880589bb118 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:885 [inline]
 #4: ffff8880589bb118 (&dev->mutex){....}-{3:3}, at: __device_attach+0x85/0x480 drivers/base/dd.c:1009
 #5: ffff8880865040d0 (&d->usb_mutex#2){+.+.}-{3:3}, at: rtl28xxu_ctrl_msg+0x57/0x630 drivers/media/usb/dvb-usb-v2/rtl28xxu.c:24
2 locks held by kworker/u4:20/4615:
 #0: ffff888018479138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
 #1: ffffc90005187d00 ((work_completion)(&sub_info->work)){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
3 locks held by kworker/0:9/8527:
 #0: ffff88814008b538 ((wq_completion)pm){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
 #1: ffffc900041afd00 ((work_completion)(&hcd->wakeup_work)){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
 #2: ffff888145bbe190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:885 [inline]
 #2: ffff888145bbe190 (&dev->mutex){....}-{3:3}, at: usb_remote_wakeup+0x1f/0xf0 drivers/usb/core/hub.c:3844
6 locks held by kworker/0:8/11569:
 #0: ffff8881436bc538 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
 #1: ffffc900033a7d00 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
 #2: ffff888145b40190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:885 [inline]
 #2: ffff888145b40190 (&dev->mutex){....}-{3:3}, at: hub_event+0x178/0x5200 drivers/usb/core/hub.c:5855
 #3: ffff888145b43500 (&port_dev->status_lock){+.+.}-{3:3}, at: usb_lock_port drivers/usb/core/hub.c:3210 [inline]
 #3: ffff888145b43500 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_port_connect drivers/usb/core/hub.c:5423 [inline]
 #3: ffff888145b43500 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_port_connect_change drivers/usb/core/hub.c:5667 [inline]
 #3: ffff888145b43500 (&port_dev->status_lock){+.+.}-{3:3}, at: port_event drivers/usb/core/hub.c:5827 [inline]
 #3: ffff888145b43500 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_event+0x2076/0x5200 drivers/usb/core/hub.c:5909
 #4: ffff888027ec2368 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_port_connect drivers/usb/core/hub.c:5424 [inline]
 #4: ffff888027ec2368 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_port_connect_change drivers/usb/core/hub.c:5667 [inline]
 #4: ffff888027ec2368 (hcd->address0_mutex){+.+.}-{3:3}, at: port_event drivers/usb/core/hub.c:5827 [inline]
 #4: ffff888027ec2368 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_event+0x20a1/0x5200 drivers/usb/core/hub.c:5909
 #5: ffffffff8e686e10 (ehci_cf_port_reset_rwsem){.+.+}-{3:3}, at: hub_port_reset+0x151/0x18d0 drivers/usb/core/hub.c:3067
3 locks held by syz.7.1347/11754:
1 lock held by syz.3.1350/11847:
 #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.4.1349/12097:
 #0: ffffffff8e2853e8 (tty_mutex){+.+.}-{3:3}, at: ptmx_open+0xcc/0x2c0 drivers/tty/pty.c:823
1 lock held by syz.8.1458/12479:
 #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.5.1710/13577:
 #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
4 locks held by udevd/13629:
 #0: ffff8880817d7790 (&p->lock){+.+.}-{3:3}, at: seq_read_iter+0x9d/0xc50 fs/seq_file.c:182
 #1: ffff8880826c6488 (&of->mutex){+.+.}-{3:3}, at: kernfs_seq_start+0x59/0x410 fs/kernfs/file.c:172
 #2: ffff8880890cc830 (kn->active#5){++++}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline]
 #2: ffff8880890cc830 (kn->active#5){++++}-{0:0}, at: kernfs_seq_start+0xae/0x410 fs/kernfs/file.c:173
 #3: ffff888055188190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:885 [inline]
 #3: ffff888055188190 (&dev->mutex){....}-{3:3}, at: uevent_show+0x16e/0x320 drivers/base/core.c:2670
1 lock held by syz.2.1848/14170:
 #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
3 locks held by modprobe/14580:

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

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 11/06/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 (17):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/11/13 23:36 linux-6.1.y c75b0cf0982c be5d1971 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in tty_open
2026/11/04 09:08 linux-6.1.y 08889840163e 5af5b6c6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in tty_open
2026/10/30 04:18 linux-6.1.y 79807e970724 b498adee .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in tty_open
2026/10/27 23:39 linux-6.1.y 79807e970724 96923c60 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in tty_open
2026/10/26 18:03 linux-6.1.y 79807e970724 168cb7a2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in tty_open
2026/09/24 08:16 linux-6.1.y 1a8763b93150 0281b448 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in tty_open
2026/09/23 01:38 linux-6.1.y 1a8763b93150 5207b90e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in tty_open
2026/09/12 00:24 linux-6.1.y cf82dcca9634 b6a5eeb7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in tty_open
2026/09/01 16:57 linux-6.1.y d64a499eea6b 587f6b29 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in tty_open
2026/08/14 23:15 linux-6.1.y e4f7d8be268e 6f9b3e89 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in tty_open
2026/08/12 12:30 linux-6.1.y e4f7d8be268e f8d35649 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in tty_open
2026/08/10 11:19 linux-6.1.y e4f7d8be268e 5d63f80b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in tty_open
2026/08/07 06:26 linux-6.1.y 03f3a99e8e93 c38879ea .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in tty_open
2026/08/07 02:51 linux-6.1.y 03f3a99e8e93 c38879ea .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in tty_open
2026/08/05 21:36 linux-6.1.y fb28aa725e05 cd5b1963 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in tty_open
2026/08/03 13:32 linux-6.1.y fb28aa725e05 6b7c9f71 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in tty_open
2026/10/01 18:38 linux-6.1.y 1a8763b93150 f5cdae2f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in tty_open
* Struck through repros no longer work on HEAD.