syzbot


INFO: task hung in pipe_release (2)

Status: upstream: reported on 2025/03/26 20:01
Reported-by: syzbot+9aaba73bda8cedfd1122@syzkaller.appspotmail.com
First crash: 49d, last: 49d
Similar bugs (13)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
android-414 INFO: task hung in pipe_release 1 2118d 2118d 0/1 auto-closed as invalid on 2019/11/24 16:38
upstream INFO: task hung in pipe_release (5) fs 160 133d 243d 0/28 auto-obsoleted due to no activity on 2025/02/21 02:48
upstream INFO: task hung in pipe_release (2) ext4 syz done 3 1715d 1746d 15/28 fixed on 2020/09/25 01:17
android-49 INFO: task hung in pipe_release (2) 1 2082d 2082d 0/3 auto-closed as invalid on 2019/12/30 22:08
linux-6.1 INFO: task hung in pipe_release 2 201d 259d 0/3 auto-obsoleted due to no activity on 2025/02/03 06:35
upstream INFO: task hung in pipe_release (4) fs C done 51 673d 673d 23/28 fixed on 2023/10/12 12:48
android-49 INFO: task hung in pipe_release 2 2311d 2223d 0/3 auto-closed as invalid on 2019/07/14 20:38
upstream INFO: task hung in pipe_release (3) fs 4 1276d 1390d 0/28 closed as invalid on 2022/02/07 19:19
upstream INFO: task hung in pipe_release fs 2 2209d 2373d 0/28 auto-closed as invalid on 2019/10/25 10:11
linux-4.19 INFO: task hung in pipe_release 1 1512d 1512d 0/1 auto-closed as invalid on 2021/07/23 11:59
linux-5.15 INFO: task hung in pipe_release 2 208d 270d 0/3 auto-obsoleted due to no activity on 2025/01/27 06:00
upstream INFO: task hung in pipe_release (6) bcachefs syz done 5 50d 76d 0/28 upstream: reported syz repro on 2025/02/27 19:55
upstream INFO: task can't die in pipe_release (2) fs 1 1568d 1564d 0/28 auto-closed as invalid on 2021/03/29 10:10

Sample crash report:
INFO: task syz.3.341:6082 blocked for more than 143 seconds.
      Not tainted 5.15.179-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.3.341       state:D stack:26640 pid: 6082 ppid:  4172 flags:0x00004000
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5029 [inline]
 __schedule+0x12c4/0x45b0 kernel/sched/core.c:6375
 schedule+0x11b/0x1f0 kernel/sched/core.c:6458
 schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6517
 __mutex_lock_common+0xe34/0x25a0 kernel/locking/mutex.c:669
 __mutex_lock kernel/locking/mutex.c:729 [inline]
 mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
 __pipe_lock fs/pipe.c:102 [inline]
 pipe_release+0x4d/0x330 fs/pipe.c:723
 __fput+0x3fe/0x8e0 fs/file_table.c:311
 task_work_run+0x129/0x1a0 kernel/task_work.c:188
 tracehook_notify_resume include/linux/tracehook.h:189 [inline]
 exit_to_user_mode_loop+0x106/0x130 kernel/entry/common.c:181
 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:0x7f4fa27af169
RSP: 002b:00007ffdb527fa88 EFLAGS: 00000246 ORIG_RAX: 00000000000001b4
RAX: 0000000000000000 RBX: 00007f4fa29c9ba0 RCX: 00007f4fa27af169
RDX: 0000000000000000 RSI: 000000000000001e RDI: 0000000000000003
RBP: 00007f4fa29c9ba0 R08: 000000000000308c R09: 00000006b527fd7f
R10: 00007f4fa29c9ac0 R11: 0000000000000246 R12: 000000000001ce93
R13: 00007f4fa29c8080 R14: ffffffffffffffff R15: 00007ffdb527fba0
 </TASK>

Showing all locks held in the system:
1 lock held by rcu_preempt/15:
 #0: ffff8880b8f3a318 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x26/0x140 kernel/sched/core.c:475
1 lock held by khungtaskd/27:
 #0: ffffffff8cb1f4e0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by getty/3926:
 #0: ffff88802aff3098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
 #1: ffffc900025c62e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6af/0x1db0 drivers/tty/n_tty.c:2158
4 locks held by kworker/1:15/4348:
 #0: ffff8880b8f3a318 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x26/0x140 kernel/sched/core.c:475
 #1: ffff8880b8f27848 (&per_cpu_ptr(group->pcpu, cpu)->seq){-.-.}-{0:0}, at: psi_task_switch+0x53d/0x810 kernel/sched/psi.c:891
 #2: ffff8880b8f28098 (&base->lock){-.-.}-{2:2}, at: kfree_rcu_monitor+0x29/0x6c0 kernel/rcu/tree.c:3378
 #3: ffff8880b8f28098 (&base->lock){-.-.}-{2:2}, at: lock_timer_base+0x120/0x260 kernel/time/timer.c:946
1 lock held by syz.3.341/6082:
 #0: ffff88807cda1868 (&pipe->mutex/1){+.+.}-{3:3}, at: __pipe_lock fs/pipe.c:102 [inline]
 #0: ffff88807cda1868 (&pipe->mutex/1){+.+.}-{3:3}, at: pipe_release+0x4d/0x330 fs/pipe.c:723
1 lock held by syz.3.341/6083:
 #0: ffff88807cda1868 (&pipe->mutex/1){+.+.}-{3:3}, at: splice_file_to_pipe+0x2a/0x3d0 fs/splice.c:1015
2 locks held by dhcpcd/6130:

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

NMI backtrace for cpu 0
CPU: 0 PID: 27 Comm: khungtaskd Not tainted 5.15.179-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
Call Trace:
 <TASK>
 __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:212 [inline]
 watchdog+0xe72/0xeb0 kernel/hung_task.c:369
 kthread+0x3f6/0x4f0 kernel/kthread.c:334
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
 </TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 5496 Comm: syz-executor Not tainted 5.15.179-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
RIP: 0010:__preempt_count_add kernel/rcu/tree.c:1119 [inline]
RIP: 0010:rcu_is_watching+0x4/0xa0 kernel/rcu/tree.c:1122
Code: 5d 41 5e 41 5f 5d c3 e8 2a b2 d4 08 41 f7 c4 00 02 00 00 75 b4 eb b3 e8 0a b2 d4 08 66 2e 0f 1f 84 00 00 00 00 00 41 57 41 56 <53> 65 ff 05 7c 22 97 7e e8 af c5 d4 08 89 c3 83 f8 08 73 72 49 bf
RSP: 0018:ffffc900034bfec0 EFLAGS: 00000002
RAX: 0000000000000000 RBX: 0000000000000001 RCX: ffffffff81a77ff5
RDX: ffff8880214c5940 RSI: 0000000000000001 RDI: 0000000000000000
RBP: 0000000000000001 R08: ffffffff81a7801d R09: fffffbfff1c153f6
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000000
R13: 0000000000000000 R14: ffff8880214c5940 R15: 0000000000000000
FS:  00005555875d3500(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fb99185efa8 CR3: 000000005c221000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <NMI>
 </NMI>
 <TASK>
 trace_user_enter+0x77/0x1b0 include/trace/events/context_tracking.h:34
 __context_tracking_enter+0x57/0x90 kernel/context_tracking.c:81
 user_enter_irqoff include/linux/context_tracking.h:41 [inline]
 __exit_to_user_mode kernel/entry/common.c:136 [inline]
 syscall_exit_to_user_mode+0x1d1/0x240 kernel/entry/common.c:309
 do_syscall_64+0x47/0xb0 arch/x86/entry/common.c:86
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7fbc80d19980
Code: 44 24 20 0f 29 44 24 30 0f 29 44 24 40 48 8b 44 24 08 ff d0 48 83 c4 50 31 c0 5b 5d 41 5c 41 5d 41 5e c3 0f 1f 80 00 00 00 00 <c3> 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 c3 66 66 2e 0f 1f
RSP: 002b:00007ffc31fe31b8 EFLAGS: 00000293
RAX: 0000000000000000 RBX: 0000000000000015 RCX: 00007fbc80e503d7
RDX: 00007ffc31fe31c0 RSI: 00007ffc31fe32f0 RDI: 0000000000000011
RBP: 00007ffc31fe37dc R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000008
R13: 00005555875e6590 R14: 000000000001c80a R15: 00007ffc31fe3830
 </TASK>

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/03/26 20:00 linux-5.15.y 0c935c049b5c 20510e88 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in pipe_release
* Struck through repros no longer work on HEAD.