syzbot


INFO: task hung in pipe_release

Status: auto-obsoleted due to no activity on 2025/01/27 06:00
Reported-by: syzbot+ac0a2f6222bf3e8bcd02@syzkaller.appspotmail.com
First crash: 164d, last: 102d
Similar bugs (11)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
android-414 INFO: task hung in pipe_release 1 2013d 2013d 0/1 auto-closed as invalid on 2019/11/24 16:38
upstream INFO: task hung in pipe_release (5) fs 160 28d 137d 0/28 moderation: reported on 2024/09/14 11:01
upstream INFO: task hung in pipe_release (2) ext4 syz done 3 1610d 1641d 15/28 fixed on 2020/09/25 01:17
android-49 INFO: task hung in pipe_release (2) 1 1977d 1977d 0/3 auto-closed as invalid on 2019/12/30 22:08
linux-6.1 INFO: task hung in pipe_release 2 95d 154d 0/3 upstream: reported on 2024/08/28 18:21
upstream INFO: task hung in pipe_release (4) fs C done 51 567d 567d 23/28 fixed on 2023/10/12 12:48
android-49 INFO: task hung in pipe_release 2 2206d 2117d 0/3 auto-closed as invalid on 2019/07/14 20:38
upstream INFO: task hung in pipe_release (3) fs 4 1170d 1284d 0/28 closed as invalid on 2022/02/07 19:19
upstream INFO: task hung in pipe_release fs 2 2103d 2268d 0/28 auto-closed as invalid on 2019/10/25 10:11
linux-4.19 INFO: task hung in pipe_release 1 1406d 1406d 0/1 auto-closed as invalid on 2021/07/23 11:59
upstream INFO: task can't die in pipe_release (2) fs 1 1462d 1458d 0/28 auto-closed as invalid on 2021/03/29 10:10

Sample crash report:
INFO: task syz.3.10:3677 blocked for more than 143 seconds.
      Not tainted 5.15.168-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.3.10        state:D stack:27064 pid: 3677 ppid:  3572 flags:0x00004000
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5027 [inline]
 __schedule+0x12c4/0x45b0 kernel/sched/core.c:6373
 schedule+0x11b/0x1f0 kernel/sched/core.c:6456
 schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6515
 __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:280
 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:0x7f8c20d71ff9
RSP: 002b:00007ffcf7971dd8 EFLAGS: 00000246 ORIG_RAX: 00000000000001b4
RAX: 0000000000000000 RBX: 00007f8c20f2ba80 RCX: 00007f8c20d71ff9
RDX: 0000000000000000 RSI: 000000000000001e RDI: 0000000000000003
RBP: 00007f8c20f2ba80 R08: 0000000000000006 R09: 00007ffcf79720cf
R10: 00000000005e8808 R11: 0000000000000246 R12: 000000000000d0e9
R13: 00007ffcf7971ee0 R14: 0000000000000032 R15: ffffffffffffffff
 </TASK>
INFO: task syz.3.10:3686 blocked for more than 145 seconds.
      Not tainted 5.15.168-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.3.10        state:D stack:28512 pid: 3686 ppid:  3572 flags:0x00004000
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5027 [inline]
 __schedule+0x12c4/0x45b0 kernel/sched/core.c:6373
 schedule+0x11b/0x1f0 kernel/sched/core.c:6456
 schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6515
 __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_fasync+0x51/0x1f0 fs/pipe.c:748
 ioctl_fioasync fs/ioctl.c:383 [inline]
 do_vfs_ioctl+0x1334/0x2b70 fs/ioctl.c:795
 __do_sys_ioctl fs/ioctl.c:872 [inline]
 __se_sys_ioctl+0x81/0x160 fs/ioctl.c:860
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f8c20d71ff9
RSP: 002b:00007f8c1f1c9038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f8c20f2a058 RCX: 00007f8c20d71ff9
RDX: 0000000020000100 RSI: 0000000000005452 RDI: 000000000000000e
RBP: 00007f8c20de4296 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f8c20f2a058 R15: 00007ffcf7971c78
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/27:
 #0: ffffffff8c91fc20 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by getty/3334:
 #0: ffff88802a00c098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
 #1: ffffc9000208e2e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6af/0x1db0 drivers/tty/n_tty.c:2158
1 lock held by dhcpcd/3381:
1 lock held by syz.3.10/3677:
 #0: ffff8880221ce868 (&pipe->mutex/1){+.+.}-{3:3}, at: __pipe_lock fs/pipe.c:102 [inline]
 #0: ffff8880221ce868 (&pipe->mutex/1){+.+.}-{3:3}, at: pipe_release+0x4d/0x330 fs/pipe.c:723
1 lock held by syz.3.10/3679:
 #0: ffff8880221ce868 (&pipe->mutex/1){+.+.}-{3:3}, at: splice_file_to_pipe+0x2a/0x3d0 fs/splice.c:1015
1 lock held by syz.3.10/3686:
 #0: ffff8880221ce868 (&pipe->mutex/1){+.+.}-{3:3}, at: __pipe_lock fs/pipe.c:102 [inline]
 #0: ffff8880221ce868 (&pipe->mutex/1){+.+.}-{3:3}, at: pipe_fasync+0x51/0x1f0 fs/pipe.c:748

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

NMI backtrace for cpu 0
CPU: 0 PID: 27 Comm: khungtaskd Not tainted 5.15.168-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
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: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
 </TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 3018 Comm: klogd Not tainted 5.15.168-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:lock_release+0x5a5/0x9a0
Code: ff 0f 85 da fc ff ff 48 8b 7c 24 18 48 8b 74 24 20 48 8b 54 24 50 e8 aa 86 00 00 49 bf 00 00 00 00 00 fc ff df 4c 8b 64 24 08 <48> 8b 5c 24 28 49 89 dd 4c 8d b4 24 90 00 00 00 48 c7 c7 20 3d 8b
RSP: 0018:ffffc90002557940 EFLAGS: 00000046
RAX: 1ffff1100fbc5c84 RBX: ffff88807de2e420 RCX: ffffc90002557903
RDX: 0000000000000001 RSI: ffff88807de2e428 RDI: ffff88807de2e458
RBP: ffffc90002557a70 R08: dffffc0000000000 R09: fffffbfff1bd2cbe
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff920004aaf34
R13: 00000000000c050d R14: e385e736b6d44918 R15: dffffc0000000000
FS:  00007f27619e7380(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 0000000028878000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <NMI>
 </NMI>
 <TASK>
 __raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:158 [inline]
 _raw_spin_unlock_irqrestore+0x75/0x130 kernel/locking/spinlock.c:194
 unix_dgram_sendmsg+0x15c1/0x2090 net/unix/af_unix.c:1933
 sock_sendmsg_nosec net/socket.c:704 [inline]
 __sock_sendmsg net/socket.c:716 [inline]
 __sys_sendto+0x564/0x720 net/socket.c:2063
 __do_sys_sendto net/socket.c:2075 [inline]
 __se_sys_sendto net/socket.c:2071 [inline]
 __x64_sys_sendto+0xda/0xf0 net/socket.c:2071
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f2761b499b5
Code: 8b 44 24 08 48 83 c4 28 48 98 c3 48 98 c3 41 89 ca 64 8b 04 25 18 00 00 00 85 c0 75 26 45 31 c9 45 31 c0 b8 2c 00 00 00 0f 05 <48> 3d 00 f0 ff ff 76 7a 48 8b 15 44 c4 0c 00 f7 d8 64 89 02 48 83
RSP: 002b:00007ffd98945be8 EFLAGS: 00000246 ORIG_RAX: 000000000000002c
RAX: ffffffffffffffda RBX: 0000000000000002 RCX: 00007f2761b499b5
RDX: 0000000000000049 RSI: 0000563d859bd750 RDI: 0000000000000003
RBP: 0000563d859b8910 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000004000 R11: 0000000000000246 R12: 0000000000000013
R13: 00007f2761cd7212 R14: 00007ffd98945ce8 R15: 0000000000000000
 </TASK>

Crashes (2):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/10/19 05:59 linux-5.15.y 584a40a22cb9 cd6fc0a3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in pipe_release
2024/08/18 07:46 linux-5.15.y 7e89efd3ae1c dbc93b08 .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.