syzbot


INFO: task hung in pipe_write (6)

Status: auto-obsoleted due to no activity on 2026/01/07 06:32
Subsystems: kernfs netfs
[Documentation on labels]
Reported-by: syzbot+5984e31a805252b3b40a@syzkaller.appspotmail.com
First crash: 330d, last: 106d
Cause bisection: introduced by (bisect log) :
commit 7ba167c4c73ed96eb002c98a9d7d49317dfb0191
Author: David Howells <dhowells@redhat.com>
Date: Mon Mar 18 16:57:31 2024 +0000

  netfs: Switch to using unsigned long long rather than loff_t

Crash: INFO: task hung in pipe_write (log)
Repro: C syz .config
  
Fix bisection: fixed by (bisect log) :
commit e8fe3f07a357c39d429e02ca34f740692d88967a
Author: Oleg Nesterov <oleg@redhat.com>
Date: Tue Aug 19 16:10:13 2025 +0000

  9p/trans_fd: p9_fd_request: kick rx thread if EPOLLIN

  
Discussions (4)
Title Replies (including bot) Last reply
[syzbot] [netfs?] INFO: task hung in pipe_write (6) 0 (2) 2025/11/02 17:38
[syzbot] Monthly netfs report (Aug 2025) 0 (1) 2025/08/29 12:52
[syzbot] Monthly netfs report (Jun 2025) 0 (1) 2025/06/23 07:30
[syzbot] Monthly netfs report (Feb 2025) 0 (1) 2025/02/23 22:20
Similar bugs (15)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in pipe_write (3) fs 1 1 2179d 2179d 0/29 auto-closed as invalid on 2020/04/25 05:37
android-44 INFO: task hung in pipe_write 1 1 2594d 2466d 0/2 auto-closed as invalid on 2019/06/05 06:19
upstream INFO: task hung in pipe_write (5) fs 1 4 422d 462d 0/29 auto-obsoleted due to no activity on 2025/02/15 05:49
android-6-12 INFO: task hung in pipe_write origin:upstream 1 C 5 73d 128d 0/1 premoderation: reported C repro on 2025/09/06 22:58
upstream INFO: task hung in rtnetlink_rcv_msg net 1 C inconclusive inconclusive 1970 553d 2516d 26/29 fixed on 2024/07/09 19:14
upstream INFO: task hung in pipe_write (2) ext4 1 C done 6 2308d 2307d 0/29 closed as invalid on 2019/09/28 02:25
upstream INFO: task hung in pipe_write fs 1 8 2538d 2652d 0/29 auto-closed as invalid on 2019/07/30 21:09
linux-4.14 INFO: task hung in pipe_write 1 C 1 1059d 1177d 0/1 upstream: reported C repro on 2022/10/24 05:45
android-44 INFO: task hung in pipe_write (2) 1 1 2234d 2234d 0/2 auto-closed as invalid on 2020/03/31 01:26
android-49 INFO: task hung in pipe_write 1 C 3 2260d 2466d 0/3 public: reported C repro on 2019/04/14 08:51
linux-4.19 INFO: task hung in pipe_write 1 C error 13 1147d 2046d 0/1 upstream: reported C repro on 2020/06/07 01:40
upstream INFO: task hung in pipe_write (4) fs 1 syz error 7 1446d 1993d 0/29 auto-obsoleted due to no activity on 2022/10/22 17:00
android-414 INFO: task hung in pipe_write 1 1 2282d 2282d 0/1 auto-closed as invalid on 2020/02/11 22:17
upstream INFO: task can't die in pipe_write (2) fs 1 1 1545d 1541d 0/29 auto-closed as invalid on 2021/12/19 10:46
upstream INFO: task can't die in pipe_write fs 1 1 1619d 1593d 0/29 auto-closed as invalid on 2021/10/06 11:40
Last patch testing requests (1)
Created Duration User Patch Repo Result
2025/03/25 02:18 24m retest repro upstream report log
Fix bisection attempts (7)
Created Duration User Patch Repo Result
2025/11/02 10:06 7h30m bisect fix upstream OK (1) job log
2025/09/29 04:38 1h53m bisect fix upstream OK (0) job log log
2025/08/29 04:21 5h24m bisect fix upstream OK (0) job log log
2025/07/20 20:50 3h04m bisect fix upstream OK (0) job log log
2025/06/16 13:31 1h58m bisect fix upstream OK (0) job log log
2025/05/17 03:41 1h55m bisect fix upstream OK (0) job log log
2025/04/11 11:30 2h20m bisect fix upstream OK (0) job log log

Sample crash report:
INFO: task kworker/1:2:970 blocked for more than 143 seconds.
      Not tainted 6.14.0-rc5-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/1:2     state:D stack:24304 pid:970   tgid:970   ppid:2      task_flags:0x4208060 flags:0x00004000
Workqueue: events p9_write_work
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5378 [inline]
 __schedule+0xf43/0x5890 kernel/sched/core.c:6765
 __schedule_loop kernel/sched/core.c:6842 [inline]
 schedule+0xe7/0x350 kernel/sched/core.c:6857
 schedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:6914
 __mutex_lock_common kernel/locking/mutex.c:662 [inline]
 __mutex_lock+0x6bd/0xb10 kernel/locking/mutex.c:730
 pipe_write+0x166/0x1b30 fs/pipe.c:456
 __kernel_write_iter+0x318/0xa90 fs/read_write.c:612
 __kernel_write fs/read_write.c:632 [inline]
 kernel_write fs/read_write.c:653 [inline]
 kernel_write+0x1f6/0x6c0 fs/read_write.c:643
 p9_fd_write net/9p/trans_fd.c:432 [inline]
 p9_write_work+0x244/0xbf0 net/9p/trans_fd.c:483
 process_one_work+0x9c5/0x1ba0 kernel/workqueue.c:3238
 process_scheduled_works kernel/workqueue.c:3319 [inline]
 worker_thread+0x6c8/0xf00 kernel/workqueue.c:3400
 kthread+0x3af/0x750 kernel/kthread.c:464
 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:148
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </TASK>

Showing all locks held in the system:
1 lock held by rcu_tasks_trace/15:
 #0: ffffffff8e1bc130 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{4:4}, at: rcu_tasks_one_gp+0x7af/0xe90 kernel/rcu/tasks.h:613
1 lock held by khungtaskd/30:
 #0: ffffffff8e1bccc0 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:337 [inline]
 #0: ffffffff8e1bccc0 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:849 [inline]
 #0: ffffffff8e1bccc0 (rcu_read_lock){....}-{1:3}, at: debug_show_all_locks+0x7f/0x390 kernel/locking/lockdep.c:6746
6 locks held by kworker/u8:2/35:
 #0: ffff88801beeb148 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work+0x1293/0x1ba0 kernel/workqueue.c:3213
 #1: ffffc90000ab7d18 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work+0x921/0x1ba0 kernel/workqueue.c:3214
 #2: ffffffff8fee1810 (pernet_ops_rwsem){++++}-{4:4}, at: cleanup_net+0xca/0xb30 net/core/net_namespace.c:606
 #3: ffffffff8fef7528 (rtnl_mutex){+.+.}-{4:4}, at: wg_netns_pre_exit+0x1b/0x230 drivers/net/wireguard/device.c:415
 #4: ffff88806420d4e8 (&wg->device_update_lock){+.+.}-{4:4}, at: wg_netns_pre_exit+0xdd/0x230 drivers/net/wireguard/device.c:420
 #5: ffffffff8e1c8138 (rcu_state.exp_mutex){+.+.}-{4:4}, at: exp_funnel_lock+0x282/0x3b0 kernel/rcu/tree_exp.h:302
3 locks held by kworker/u8:4/81:
 #0: ffff88801b081148 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x1293/0x1ba0 kernel/workqueue.c:3213
 #1: ffffc9000216fd18 ((linkwatch_work).work){+.+.}-{0:0}, at: process_one_work+0x921/0x1ba0 kernel/workqueue.c:3214
 #2: ffffffff8fef7528 (rtnl_mutex){+.+.}-{4:4}, at: linkwatch_event+0x51/0xc0 net/core/link_watch.c:285
3 locks held by kworker/1:2/970:
 #0: ffff88801b078d48 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x1293/0x1ba0 kernel/workqueue.c:3213
 #1: ffffc90003b7fd18 ((work_completion)(&m->wq)){+.+.}-{0:0}, at: process_one_work+0x921/0x1ba0 kernel/workqueue.c:3214
 #2: ffff888032082868 (&pipe->mutex){+.+.}-{4:4}, at: pipe_write+0x166/0x1b30 fs/pipe.c:456
2 locks held by getty/5575:
 #0: 
ffff88814dab60a0
 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x24/0x80 drivers/tty/tty_ldisc.c:243
 #1: ffffc90002fde2f0 (&ldata->atomic_read_lock){+.+.}-{4:4}, at: n_tty_read+0xfba/0x1480 drivers/tty/n_tty.c:2211
5 locks held by kworker/1:6/5925:
 #0: ffff888023298d48 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x1293/0x1ba0 kernel/workqueue.c:3213
 #1: ffffc90004a7fd18 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x921/0x1ba0 kernel/workqueue.c:3214
 #2: ffff888144b88190 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:1030 [inline]
 #2: ffff888144b88190 (&dev->mutex){....}-{4:4}, at: hub_event+0x1c1/0x4e10 drivers/usb/core/hub.c:5861
 #3: ffff888028e7b190 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:1030 [inline]
 #3: ffff888028e7b190 (&dev->mutex){....}-{4:4}, at: __device_attach+0x7f/0x4b0 drivers/base/dd.c:1005
 #4: ffff888075dba160 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:1030 [inline]
 #4: ffff888075dba160 (&dev->mutex){....}-{4:4}, at: __device_attach+0x7f/0x4b0 drivers/base/dd.c:1005
4 locks held by udevd/5943:
 #0: ffff88804947a540 (&p->lock){+.+.}-{4:4}, at: seq_read_iter+0xd8/0x12b0 fs/seq_file.c:182
 #1: ffff888025256488 (&of->mutex#2){+.+.}-{4:4}, at: kernfs_seq_start+0x4d/0x240 fs/kernfs/file.c:154
 #2: ffff888076ee1698 (kn->active#5){++++}-{0:0}, at: kernfs_seq_start+0x71/0x240 fs/kernfs/file.c:155
 #3: ffff888028e7b190 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:1030 [inline]
 #3: ffff888028e7b190 (&dev->mutex){....}-{4:4}, at: uevent_show+0x188/0x3b0 drivers/base/core.c:2729
2 locks held by syz.1.404/7566:
 #0: ffff888032082868 (&pipe->mutex){+.+.}-{4:4}, at: pipe_write+0x166/0x1b30 fs/pipe.c:456
 #1: ffff88807e0982e8 (mapping.invalidate_lock#3){.+.+}-{4:4}, at: filemap_invalidate_lock_shared include/linux/fs.h:932 [inline]
 #1: ffff88807e0982e8 (mapping.invalidate_lock#3){.+.+}-{4:4}, at: page_cache_ra_unbounded+0x173/0x7d0 mm/readahead.c:229

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

NMI backtrace for cpu 0
CPU: 0 UID: 0 PID: 30 Comm: khungtaskd Not tainted 6.14.0-rc5-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:94 [inline]
 dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120
 nmi_cpu_backtrace+0x27b/0x390 lib/nmi_backtrace.c:113
 nmi_trigger_cpumask_backtrace+0x29c/0x300 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:162 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:236 [inline]
 watchdog+0xf62/0x12b0 kernel/hung_task.c:399
 kthread+0x3af/0x750 kernel/kthread.c:464
 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:148
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 UID: 0 PID: 1146 Comm: kworker/u8:5 Not tainted 6.14.0-rc5-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
Workqueue: bat_events batadv_nc_worker
RIP: 0010:__lock_release kernel/locking/lockdep.c:5527 [inline]
RIP: 0010:lock_release+0x227/0x6f0 kernel/locking/lockdep.c:5872
Code: 03 0f 8e 70 04 00 00 45 8b af e8 0a 00 00 45 85 ed 0f 84 01 03 00 00 48 8d 4c 24 50 44 89 ea 4c 89 e6 4c 89 ff e8 a9 04 ff ff <48> 85 c0 48 89 c5 0f 84 e2 02 00 00 48 8d 78 24 48 b8 00 00 00 00
RSP: 0018:ffffc9000420f9d8 EFLAGS: 00000097
RAX: ffff8880280d2f80 RBX: 1ffff92000841f3d RCX: ffffc9000420fa28
RDX: 0000000000000004 RSI: ffff888031928bd8 RDI: ffff8880280d2f80
RBP: 0000000000000007 R08: 0000000000000000 R09: fffffbfff20c4b22
R10: ffffffff90625917 R11: 0000000000000002 R12: ffff888031928bd8
R13: 0000000000000003 R14: ffff8880280d2f28 R15: ffff8880280d2440
FS:  0000000000000000(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2fbecff8 CR3: 000000000df80000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <NMI>
 </NMI>
 <TASK>
 __raw_spin_unlock_bh include/linux/spinlock_api_smp.h:165 [inline]
 _raw_spin_unlock_bh+0x16/0x30 kernel/locking/spinlock.c:210
 spin_unlock_bh include/linux/spinlock.h:396 [inline]
 batadv_nc_purge_paths+0x1c6/0x390 net/batman-adv/network-coding.c:471
 batadv_nc_worker+0x913/0x1060 net/batman-adv/network-coding.c:720
 process_one_work+0x9c5/0x1ba0 kernel/workqueue.c:3238
 process_scheduled_works kernel/workqueue.c:3319 [inline]
 worker_thread+0x6c8/0xf00 kernel/workqueue.c:3400
 kthread+0x3af/0x750 kernel/kthread.c:464
 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:148
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </TASK>

Crashes (10):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/03/03 18:30 upstream 7eb172143d55 c3901742 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in pipe_write
2025/03/03 04:46 upstream 7eb172143d55 c3901742 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in pipe_write
2025/02/17 01:15 upstream ad1b832bf1cf 40a34ec9 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in pipe_write
2025/02/16 12:22 upstream 496659003dac 40a34ec9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in pipe_write
2025/03/11 02:08 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 0a6021b3fc20 16256247 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in pipe_write
2025/03/10 23:47 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 0a6021b3fc20 16256247 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in pipe_write
2025/03/10 16:22 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 77c95b8c7a16 16256247 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in pipe_write
2025/03/06 13:46 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 14d05f12084d 831e3629 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in pipe_write
2025/02/21 19:04 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci a1c24ab82279 0808a665 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in pipe_write
2025/02/17 18:41 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci a64dcfb451e2 9be4ace3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in pipe_write
* Struck through repros no longer work on HEAD.