syzbot


INFO: task hung in tty_release_struct (4)

Status: auto-obsoleted due to no activity on 2023/01/03 08:49
Subsystems: serial
[Documentation on labels]
First crash: 618d, last: 581d
Similar bugs (8)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.19 INFO: task hung in tty_release_struct 1 502d 502d 0/1 auto-obsoleted due to no activity on 2023/04/15 07:55
linux-4.14 INFO: task hung in tty_release_struct 2 1462d 1572d 0/1 auto-closed as invalid on 2020/08/28 17:40
upstream INFO: task hung in tty_release_struct serial 2 1386d 1393d 0/26 auto-closed as invalid on 2020/10/13 06:21
upstream INFO: task hung in tty_release_struct (6) serial 1 107d 107d 0/26 auto-obsoleted due to no activity on 2024/04/13 21:30
upstream INFO: task hung in tty_release_struct (2) serial 7 820d 956d 0/26 closed as invalid on 2022/02/07 19:19
upstream INFO: task hung in tty_release_struct (3) serial 3 762d 806d 0/26 auto-closed as invalid on 2022/06/29 20:46
android-414 INFO: task hung in tty_release_struct 7 1967d 1845d 0/1 auto-closed as invalid on 2019/06/10 11:00
upstream INFO: task hung in tty_release_struct (5) serial 1 296d 296d 0/26 auto-obsoleted due to no activity on 2023/10/07 22:46

Sample crash report:
INFO: task syz-executor.5:10098 blocked for more than 143 seconds.
      Not tainted 6.0.0-rc7-syzkaller-00068-g49c13ed0316d #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.5  state:D stack:27792 pid:10098 ppid:  3649 flags:0x00004004
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5182 [inline]
 __schedule+0xadf/0x52b0 kernel/sched/core.c:6494
 schedule+0xda/0x1b0 kernel/sched/core.c:6570
 schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6629
 __mutex_lock_common kernel/locking/mutex.c:679 [inline]
 __mutex_lock+0xa44/0x1350 kernel/locking/mutex.c:747
 tty_release_struct+0xa9/0xe0 drivers/tty/tty_io.c:1704
 tty_release+0xc70/0x1200 drivers/tty/tty_io.c:1865
 __fput+0x277/0x9d0 fs/file_table.c:320
 task_work_run+0xdd/0x1a0 kernel/task_work.c:177
 resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
 exit_to_user_mode_loop kernel/entry/common.c:169 [inline]
 exit_to_user_mode_prepare+0x23c/0x250 kernel/entry/common.c:201
 __syscall_exit_to_user_mode_work kernel/entry/common.c:283 [inline]
 syscall_exit_to_user_mode+0x19/0x50 kernel/entry/common.c:294
 do_syscall_64+0x42/0xb0 arch/x86/entry/common.c:86
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f759423c37b
RSP: 002b:00007f75948dfb80 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 0000000000000007 RCX: 00007f759423c37b
RDX: 0000001b2e520000 RSI: 00007f7594200000 RDI: 0000000000000006
RBP: 00007f75943ad980 R08: 0000000000000000 R09: 0000000001739d1c
R10: 00007ffde4183090 R11: 0000000000000293 R12: 00000000000cd825
R13: 00007f75948dfc80 R14: 00007f75943ac050 R15: 0000000000000032
 </TASK>
INFO: task syz-executor.1:10119 blocked for more than 143 seconds.
      Not tainted 6.0.0-rc7-syzkaller-00068-g49c13ed0316d #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.1  state:D stack:28456 pid:10119 ppid:  3654 flags:0x00000004
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5182 [inline]
 __schedule+0xadf/0x52b0 kernel/sched/core.c:6494
 schedule+0xda/0x1b0 kernel/sched/core.c:6570
 schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6629
 __mutex_lock_common kernel/locking/mutex.c:679 [inline]
 __mutex_lock+0xa44/0x1350 kernel/locking/mutex.c:747
 ptmx_open drivers/tty/pty.c:823 [inline]
 ptmx_open+0xfd/0x360 drivers/tty/pty.c:790
 chrdev_open+0x266/0x770 fs/char_dev.c:414
 do_dentry_open+0x4a4/0x13a0 fs/open.c:880
 do_open fs/namei.c:3557 [inline]
 path_openat+0x1c92/0x28f0 fs/namei.c:3691
 do_filp_open+0x1b6/0x400 fs/namei.c:3718
 do_sys_openat2+0x16d/0x4c0 fs/open.c:1313
 do_sys_open fs/open.c:1329 [inline]
 __do_sys_openat fs/open.c:1345 [inline]
 __se_sys_openat fs/open.c:1340 [inline]
 __x64_sys_openat+0x13f/0x1f0 fs/open.c:1340
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fb33de8a5a9
RSP: 002b:00007fb33ef86168 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007fb33dfac050 RCX: 00007fb33de8a5a9
RDX: 0000000000000000 RSI: 0000000020000140 RDI: ffffffffffffff9c
RBP: 00007fb33dee5560 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fb33e4dfb1f R14: 00007fb33ef86300 R15: 0000000000022000
 </TASK>

Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/13:
 #0: ffffffff8bf888b0 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x26/0xc70 kernel/rcu/tasks.h:507
1 lock held by rcu_tasks_trace/14:
 #0: ffffffff8bf885b0 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x26/0xc70 kernel/rcu/tasks.h:507
1 lock held by khungtaskd/29:
 #0: ffffffff8bf89400 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x53/0x260 kernel/locking/lockdep.c:6492
2 locks held by getty/3285:
 #0: ffff888026944098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x22/0x80 drivers/tty/tty_ldisc.c:244
 #1: ffffc90002d232f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0xef0/0x13e0 drivers/tty/n_tty.c:2177
2 locks held by kworker/u4:8/4536:
3 locks held by syz-executor.3/10097:
1 lock held by syz-executor.5/10098:
 #0: ffffffff8ca0c748 (tty_mutex){+.+.}-{3:3}, at: tty_release_struct+0xa9/0xe0 drivers/tty/tty_io.c:1704
1 lock held by syz-executor.1/10119:
 #0: ffffffff8ca0c748 (tty_mutex){+.+.}-{3:3}, at: ptmx_open drivers/tty/pty.c:823 [inline]
 #0: ffffffff8ca0c748 (tty_mutex){+.+.}-{3:3}, at: ptmx_open+0xfd/0x360 drivers/tty/pty.c:790
1 lock held by syz-executor.1/10204:
 #0: ffffffff8ca0c748 (tty_mutex){+.+.}-{3:3}, at: ptmx_open drivers/tty/pty.c:823 [inline]
 #0: ffffffff8ca0c748 (tty_mutex){+.+.}-{3:3}, at: ptmx_open+0xfd/0x360 drivers/tty/pty.c:790
1 lock held by syz-executor.3/10338:

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

NMI backtrace for cpu 1
CPU: 1 PID: 29 Comm: khungtaskd Not tainted 6.0.0-rc7-syzkaller-00068-g49c13ed0316d #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/26/2022
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
 nmi_cpu_backtrace.cold+0x46/0x14f lib/nmi_backtrace.c:111
 nmi_trigger_cpumask_backtrace+0x206/0x250 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+0xc18/0xf50 kernel/hung_task.c:369
 kthread+0x2e4/0x3a0 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
 </TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 4536 Comm: kworker/u4:8 Not tainted 6.0.0-rc7-syzkaller-00068-g49c13ed0316d #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/26/2022
Workqueue: bat_events batadv_nc_worker
RIP: 0010:arch_atomic_read arch/x86/include/asm/atomic.h:29 [inline]
RIP: 0010:rcu_dynticks_curr_cpu_in_eqs include/linux/context_tracking.h:121 [inline]
RIP: 0010:rcu_is_watching+0x58/0xb0 kernel/rcu/tree.c:718
Code: 48 89 fa 48 c1 ea 03 80 3c 02 00 75 54 48 03 1c ed e0 28 a2 8b 48 b8 00 00 00 00 00 fc ff df 48 89 da 48 c1 ea 03 0f b6 14 02 <48> 89 d8 83 e0 07 83 c0 03 38 d0 7c 04 84 d2 75 1c 8b 03 c1 e8 02
RSP: 0018:ffffc90003457b70 EFLAGS: 00000a02
RAX: dffffc0000000000 RBX: ffff8880b9a34c48 RCX: ffffffff815f7cf8
RDX: 0000000000000000 RSI: 0000000000000002 RDI: ffffffff8ba228e0
RBP: 0000000000000000 R08: 0000000000000000 R09: ffffffff8ddee457
R10: fffffbfff1bbdc8a R11: 0000000000000000 R12: 0000000000000001
R13: 0000000000000000 R14: ffffffff8bf89400 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f7d4f413718 CR3: 000000000bc8e000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 rcu_read_lock_held_common kernel/rcu/update.c:108 [inline]
 rcu_read_lock_sched_held+0x1c/0x70 kernel/rcu/update.c:123
 trace_lock_acquire include/trace/events/lock.h:24 [inline]
 lock_acquire+0x480/0x570 kernel/locking/lockdep.c:5637
 rcu_lock_acquire include/linux/rcupdate.h:280 [inline]
 rcu_read_lock include/linux/rcupdate.h:706 [inline]
 batadv_nc_purge_orig_hash net/batman-adv/network-coding.c:408 [inline]
 batadv_nc_worker+0x12d/0xfa0 net/batman-adv/network-coding.c:719
 process_one_work+0x991/0x1610 kernel/workqueue.c:2289
 worker_thread+0x665/0x1080 kernel/workqueue.c:2436
 kthread+0x2e4/0x3a0 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
 </TASK>

Crashes (2):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2022/09/28 14:22 upstream 49c13ed0316d e2556bc3 .config console log report info ci-upstream-kasan-gce INFO: task hung in tty_release_struct
2022/08/22 00:25 upstream e3f259d33c0e 26a13b38 .config console log report info ci-upstream-kasan-gce INFO: task hung in tty_release_struct
* Struck through repros no longer work on HEAD.