syzbot


INFO: task hung in pipe_release

Status: upstream: reported on 2024/08/18 07:46
Reported-by: syzbot+ac0a2f6222bf3e8bcd02@syzkaller.appspotmail.com
First crash: 53d, last: 53d
Similar bugs (11)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
android-414 INFO: task hung in pipe_release 1 1901d 1901d 0/1 auto-closed as invalid on 2019/11/24 16:38
upstream INFO: task hung in pipe_release (5) fs 90 8h58m 26d 0/28 moderation: reported on 2024/09/14 11:01
upstream INFO: task hung in pipe_release (2) ext4 syz done 3 1498d 1529d 15/28 fixed on 2020/09/25 01:17
android-49 INFO: task hung in pipe_release (2) 1 1865d 1865d 0/3 auto-closed as invalid on 2019/12/30 22:08
linux-6.1 INFO: task hung in pipe_release 1 42d 42d 0/3 upstream: reported on 2024/08/28 18:21
upstream INFO: task hung in pipe_release (4) fs C done 51 456d 456d 23/28 fixed on 2023/10/12 12:48
android-49 INFO: task hung in pipe_release 2 2094d 2006d 0/3 auto-closed as invalid on 2019/07/14 20:38
upstream INFO: task hung in pipe_release (3) fs 4 1059d 1173d 0/28 closed as invalid on 2022/02/07 19:19
upstream INFO: task hung in pipe_release fs 2 1992d 2156d 0/28 auto-closed as invalid on 2019/10/25 10:11
linux-4.19 INFO: task hung in pipe_release 1 1295d 1295d 0/1 auto-closed as invalid on 2021/07/23 11:59
upstream INFO: task can't die in pipe_release (2) fs 1 1351d 1347d 0/28 auto-closed as invalid on 2021/03/29 10:10

Sample crash report:
INFO: task syz.2.41:3757 blocked for more than 143 seconds.
      Not tainted 5.15.164-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.2.41        state:D stack:27064 pid: 3757 ppid:  3573 flags:0x00004000
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5030 [inline]
 __schedule+0x12c4/0x45b0 kernel/sched/core.c:6376
 schedule+0x11b/0x1f0 kernel/sched/core.c:6459
 schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6518
 __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:164
 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:0x7fe11c2eae79
RSP: 002b:00007ffda8e76238 EFLAGS: 00000246 ORIG_RAX: 00000000000001b4
RAX: 0000000000000000 RBX: 00007fe11c488a80 RCX: 00007fe11c2eae79
RDX: 0000000000000000 RSI: 000000000000001e RDI: 0000000000000003
RBP: 00007fe11c488a80 R08: 0000000000000006 R09: 00007ffda8e7651f
R10: 00000000003ffd3c R11: 0000000000000246 R12: 0000000000010670
R13: 00007ffda8e76330 R14: 00007ffda8e76350 R15: ffffffffffffffff
 </TASK>

Showing all locks held in the system:
2 locks held by kworker/u4:0/9:
1 lock held by khungtaskd/27:
 #0: ffffffff8c91fb20 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by getty/3324:
 #0: ffff88802463f098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
 #1: ffffc900024b32e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6af/0x1db0 drivers/tty/n_tty.c:2158
1 lock held by syz.2.41/3757:
 #0: ffff888078a68068 (&pipe->mutex/1){+.+.}-{3:3}, at: __pipe_lock fs/pipe.c:102 [inline]
 #0: ffff888078a68068 (&pipe->mutex/1){+.+.}-{3:3}, at: pipe_release+0x4d/0x330 fs/pipe.c:723
1 lock held by syz.2.41/3758:
 #0: ffff888078a68068 (&pipe->mutex/1){+.+.}-{3:3}, at: splice_file_to_pipe+0x2a/0x3d0 fs/splice.c:1015

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

NMI backtrace for cpu 0
CPU: 0 PID: 27 Comm: khungtaskd Not tainted 5.15.164-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/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: 3752 Comm: kworker/u4:10 Not tainted 5.15.164-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
Workqueue: phy8 ieee80211_iface_work
RIP: 0010:hlock_class kernel/locking/lockdep.c:197 [inline]
RIP: 0010:__lock_acquire+0xfb7/0x1ff0 kernel/locking/lockdep.c:5008
Code: 0e 00 00 8b 1b 81 e3 ff 1f 00 00 89 d8 c1 e8 06 48 8d 3c c5 c0 00 c7 8f be 08 00 00 00 e8 b1 74 67 00 48 0f a3 1d 99 3e 64 0e <0f> 83 be 01 00 00 48 8d 04 5b 48 c1 e0 06 48 8d 98 c0 5f 96 8f 48
RSP: 0018:ffffc90002ea7660 EFLAGS: 00000057
RAX: 0000000000000001 RBX: 0000000000000355 RCX: ffffffff8162c21f
RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffffff8fc70128
RBP: 355987511a8bfc68 R08: dffffc0000000000 R09: fffffbfff1f8e026
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000003
R13: ffff888021dca8a8 R14: ffff888021dc9dc0 R15: ffff888021dca948
FS:  0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000556db5d13680 CR3: 000000005d6a2000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <NMI>
 </NMI>
 <TASK>
 lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623
 __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
 _raw_spin_lock_irqsave+0xd1/0x120 kernel/locking/spinlock.c:162
 lock_timer_base+0x120/0x260 kernel/time/timer.c:946
 __mod_timer+0x4a6/0xeb0 kernel/time/timer.c:993
 ieee80211_sta_merge_ibss net/mac80211/ibss.c:1299 [inline]
 ieee80211_ibss_work+0x48b/0x1480 net/mac80211/ibss.c:1713
 process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2310
 worker_thread+0xaca/0x1280 kernel/workqueue.c:2457
 kthread+0x3f6/0x4f0 kernel/kthread.c:334
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
 </TASK>

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
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.