INFO: task syz-executor104:6342 blocked for more than 143 seconds. Not tainted 5.15.173-syzkaller #0 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:syz-executor104 state:D stack:21024 pid: 6342 ppid: 4183 flags:0x00004002 Call Trace: context_switch kernel/sched/core.c:5027 [inline] __schedule+0x12c4/0x45b0 kernel/sched/core.c:6373 schedule+0x11b/0x1f0 kernel/sched/core.c:6456 perf_pending_task_sync+0x13c/0x1c0 kernel/events/core.c:5127 _free_event+0x34/0xe60 kernel/events/core.c:5133 put_event kernel/events/core.c:5258 [inline] perf_event_release_kernel+0x873/0x900 kernel/events/core.c:5383 perf_release+0x37/0x40 kernel/events/core.c:5393 __fput+0x3fe/0x8e0 fs/file_table.c:280 task_work_run+0x129/0x1a0 kernel/task_work.c:188 exit_task_work include/linux/task_work.h:33 [inline] do_exit+0x6a3/0x2480 kernel/exit.c:874 do_group_exit+0x144/0x310 kernel/exit.c:996 get_signal+0xc66/0x14e0 kernel/signal.c:2900 arch_do_signal_or_restart+0xc3/0x1890 arch/x86/kernel/signal.c:867 handle_signal_work kernel/entry/common.c:154 [inline] exit_to_user_mode_loop+0x97/0x130 kernel/entry/common.c:178 exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:214 __syscall_exit_to_user_mode_work kernel/entry/common.c:296 [inline] syscall_exit_to_user_mode+0x5d/0x240 kernel/entry/common.c:307 do_syscall_64+0x47/0xb0 arch/x86/entry/common.c:86 entry_SYSCALL_64_after_hwframe+0x66/0xd0 RIP: 0033:0x7f01f684d469 RSP: 002b:00007fff6b204a58 EFLAGS: 00000246 ORIG_RAX: 000000000000012a RAX: 0000000000000003 RBX: 0000000000000003 RCX: 00007f01f684d469 RDX: 00000000ffffffff RSI: 0000000000000000 RDI: 0000000020000000 RBP: 0000000000000000 R08: 0000000000000000 R09: 00007fff6b204a88 R10: 00000000ffffffff R11: 0000000000000246 R12: 0000000000033bb4 R13: 00007fff6b204a84 R14: 00007fff6b204aa0 R15: 00007fff6b204a90 Showing all locks held in the system: 1 lock held by khungtaskd/27: #0: ffffffff8cb1fc60 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30 2 locks held by getty/3926: #0: ffff88802b063098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252 #1: ffffc900026362e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6af/0x1db0 drivers/tty/n_tty.c:2158 ============================================= NMI backtrace for cpu 0 CPU: 0 PID: 27 Comm: khungtaskd Not tainted 5.15.173-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1e3/0x2d0 lib/dump_stack.c:106 nmi_cpu_backtrace+0x46a/0x4a0 lib/nmi_backtrace.c:111 nmi_trigger_cpumask_backtrace+0x181/0x2a0 lib/nmi_backtrace.c:62 trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline] check_hung_uninterruptible_tasks kernel/hung_task.c:210 [inline] watchdog+0xe72/0xeb0 kernel/hung_task.c:295 kthread+0x3f6/0x4f0 kernel/kthread.c:334 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287 Sending NMI from CPU 0 to CPUs 1: NMI backtrace for cpu 1 skipped: idling at native_safe_halt arch/x86/include/asm/irqflags.h:51 [inline] NMI backtrace for cpu 1 skipped: idling at arch_safe_halt arch/x86/include/asm/irqflags.h:89 [inline] NMI backtrace for cpu 1 skipped: idling at acpi_safe_halt drivers/acpi/processor_idle.c:108 [inline] NMI backtrace for cpu 1 skipped: idling at acpi_idle_do_entry+0x10f/0x340 drivers/acpi/processor_idle.c:562