INFO: task hung in pipe_write

Status: upstream: reported C repro on 2020/06/07 01:40
Reported-by: syzbot+eb4579cce1e26940e2e1@syzkaller.appspotmail.com
First crash: 2246d, last: 1347d
Fix bisection: failed (error log, bisect log)
  
▶ ▼ 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 2379d 2379d 0/29 auto-closed as invalid on 2020/04/25 05:37
android-44 INFO: task hung in pipe_write 1 1 2794d 2666d 0/2 auto-closed as invalid on 2019/06/05 06:19
upstream INFO: task hung in pipe_write (5) fs 1 4 622d 662d 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 syz, C 5 273d 328d 0/1 auto-obsoleted due to no activity on 2026/02/21 10:27
upstream INFO: task hung in rtnetlink_rcv_msg net 1 syz, C inconclusive inconclusive 1970 753d 2716d 26/29 fixed on 2024/07/09 19:14
upstream INFO: task hung in pipe_write (2) ext4 1 syz, C done 6 2508d 2507d 0/29 closed as invalid on 2019/09/28 02:25
upstream INFO: task hung in pipe_write fs 1 8 2738d 2852d 0/29 auto-closed as invalid on 2019/07/30 21:09
linux-4.14 INFO: task hung in pipe_write 1 syz, C 1 1260d 1377d 0/1 upstream: reported C repro on 2022/10/24 05:45
android-44 INFO: task hung in pipe_write (2) 1 1 2434d 2434d 0/2 auto-closed as invalid on 2020/03/31 01:26
android-49 INFO: task hung in pipe_write 1 syz, C 3 2460d 2666d 0/3 public: reported C repro on 2019/04/14 08:51
upstream INFO: task hung in pipe_write (6) kernfs netfs 1 syz, C done done 10 306d 529d 0/29 auto-obsoleted due to no activity on 2026/01/07 06:32
upstream INFO: task hung in pipe_write (4) fs 1 syz error 7 1646d 2193d 0/29 auto-obsoleted due to no activity on 2022/10/22 17:00
android-414 INFO: task hung in pipe_write 1 1 2482d 2482d 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 1746d 1742d 0/29 auto-closed as invalid on 2021/12/19 10:46
upstream INFO: task can't die in pipe_write fs 1 1 1819d 1793d 0/29 auto-closed as invalid on 2021/10/06 11:40
▶ ▼ Fix bisection attempts (17)
Created Duration User Patch Repo Result
2021/10/31 10:31 13m bisect fix linux-4.19.y error job log
2021/09/23 10:58 36m bisect fix linux-4.19.y OK (0) job log log
2021/08/24 10:12 37m bisect fix linux-4.19.y OK (0) job log log
2021/07/25 05:27 34m bisect fix linux-4.19.y OK (0) job log log
2021/06/25 04:51 35m bisect fix linux-4.19.y OK (0) job log log
2021/05/26 04:11 40m bisect fix linux-4.19.y OK (0) job log log
2021/04/26 03:27 43m bisect fix linux-4.19.y OK (0) job log log
2021/03/26 21:30 33m bisect fix linux-4.19.y OK (0) job log log
2021/02/24 15:39 36m bisect fix linux-4.19.y OK (0) job log log
2021/02/03 06:44 1m bisect fix linux-4.19.y error job log
2021/01/04 06:09 35m bisect fix linux-4.19.y OK (0) job log log
2020/12/05 00:00 39m bisect fix linux-4.19.y OK (0) job log log
2020/11/04 13:55 37m bisect fix linux-4.19.y OK (0) job log log
2020/10/05 10:17 31m bisect fix linux-4.19.y OK (0) job log log
2020/09/05 06:56 38m bisect fix linux-4.19.y OK (0) job log log
2020/08/06 02:17 38m bisect fix linux-4.19.y OK (0) job log log
2020/07/07 01:39 37m bisect fix linux-4.19.y OK (0) job log log

Sample crash report:
INFO: task syz-executor297:8097 blocked for more than 140 seconds.
      Not tainted 4.19.211-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor297 D27696  8097   8095 0x00000004
Call Trace:
 context_switch kernel/sched/core.c:2828 [inline]
 __schedule+0x887/0x2040 kernel/sched/core.c:3517
 schedule+0x8d/0x1b0 kernel/sched/core.c:3561
 schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:3619
 __mutex_lock_common kernel/locking/mutex.c:1016 [inline]
 __mutex_lock+0x5f0/0x1190 kernel/locking/mutex.c:1078
 pipe_lock_nested fs/pipe.c:77 [inline]
 pipe_lock fs/pipe.c:85 [inline]
 pipe_wait+0x1bd/0x1e0 fs/pipe.c:133
 pipe_write+0x5c3/0xf80 fs/pipe.c:500
 call_write_iter include/linux/fs.h:1821 [inline]
 new_sync_write fs/read_write.c:474 [inline]
 __vfs_write+0x51b/0x770 fs/read_write.c:487
 vfs_write+0x1f3/0x540 fs/read_write.c:549
 ksys_write+0x12b/0x2a0 fs/read_write.c:599
 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
 entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7f50c2931b29
Code: Bad RIP value.
RSP: 002b:00007f50c28e32f8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f50c29b9428 RCX: 00007f50c2931b29
RDX: 00000000fffffecc RSI: 0000000020000000 RDI: 0000000000000004
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f50c29b9420
R13: 00007ffed35eafdf R14: 00007f50c29b942c R15: 00007f50c2987074

Showing all locks held in the system:
1 lock held by khungtaskd/1570:
 #0: 000000005519c19a (rcu_read_lock){....}, at: debug_show_all_locks+0x53/0x265 kernel/locking/lockdep.c:4441
1 lock held by in:imklog/7766:
 #0: 00000000f7d75f86 (&f->f_pos_lock){+.+.}, at: __fdget_pos+0x26f/0x310 fs/file.c:767
1 lock held by syz-executor297/8097:
 #0: 0000000089367ee1 (&pipe->mutex/1){+.+.}, at: pipe_lock_nested fs/pipe.c:77 [inline]
 #0: 0000000089367ee1 (&pipe->mutex/1){+.+.}, at: pipe_lock fs/pipe.c:85 [inline]
 #0: 0000000089367ee1 (&pipe->mutex/1){+.+.}, at: pipe_wait+0x1bd/0x1e0 fs/pipe.c:133
2 locks held by syz-executor297/8098:

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

NMI backtrace for cpu 1
CPU: 1 PID: 1570 Comm: khungtaskd Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/11/2022
Call Trace:
 __dump_stack lib/dump_stack.c:77 [inline]
 dump_stack+0x1fc/0x2ef lib/dump_stack.c:118
 nmi_cpu_backtrace.cold+0x63/0xa2 lib/nmi_backtrace.c:101
 nmi_trigger_cpumask_backtrace+0x1a6/0x1f0 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:146 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:203 [inline]
 watchdog+0x991/0xe60 kernel/hung_task.c:287
 kthread+0x33f/0x460 kernel/kthread.c:259
 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 8098 Comm: syz-executor297 Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/11/2022
RIP: 0010:hlock_class kernel/locking/lockdep.c:152 [inline]
RIP: 0010:mark_lock+0x73/0x1160 kernel/locking/lockdep.c:3106
Code: 45 20 66 a9 ff 1f 74 7c 48 ba 00 00 00 00 00 fc ff df 4c 89 f1 48 c1 e9 03 0f b6 14 11 84 d2 74 09 80 fa 03 0f 8e d2 07 00 00 <25> ff 1f 00 00 48 69 d8 50 01 00 00 48 81 eb 50 01 00 00 48 81 c3
RSP: 0018:ffff888092107148 EFLAGS: 00000046
RAX: 00000000000004f3 RBX: 0000000000000000 RCX: 1ffff1101648c5d5
RDX: 0000000000000000 RSI: ffff8880b2462e88 RDI: ffff8880b2462600
RBP: ffff8880b2462e88 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000040
R13: ffff8880b2462600 R14: ffff8880b2462ea8 R15: 0000000000000006
FS:  00007f50c28c2700(0000) GS:ffff8880ba000000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f86e5135000 CR3: 00000000b4b4a000 CR4: 00000000003406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 mark_held_locks+0xa6/0xf0 kernel/locking/lockdep.c:2810
 __trace_hardirqs_on_caller kernel/locking/lockdep.c:2839 [inline]
 lockdep_hardirqs_on+0x3a8/0x5c0 kernel/locking/lockdep.c:2884
 slab_alloc_node mm/slab.c:3334 [inline]
 kmem_cache_alloc_node_trace+0x2da/0x3b0 mm/slab.c:3666
 __do_kmalloc_node mm/slab.c:3688 [inline]
 __kmalloc_node_track_caller+0x38/0x70 mm/slab.c:3703
 __kmalloc_reserve net/core/skbuff.c:137 [inline]
 pskb_expand_head+0x159/0xf20 net/core/skbuff.c:1473
 netlink_trim+0x200/0x250 net/netlink/af_netlink.c:1307
 netlink_unicast+0xb9/0x690 net/netlink/af_netlink.c:1341
 ip_set_protocol+0x3c4/0x540 net/netfilter/ipset/ip_set_core.c:1840
 nfnetlink_rcv_msg+0xc4f/0xf60 net/netfilter/nfnetlink.c:233
 netlink_rcv_skb+0x160/0x440 net/netlink/af_netlink.c:2463
 nfnetlink_rcv+0x1b2/0x420 net/netfilter/nfnetlink.c:565
 netlink_unicast_kernel net/netlink/af_netlink.c:1325 [inline]
 netlink_unicast+0x4d5/0x690 net/netlink/af_netlink.c:1351
 netlink_sendmsg+0x6c3/0xc50 net/netlink/af_netlink.c:1917
 sock_sendmsg_nosec net/socket.c:651 [inline]
 sock_sendmsg+0xc3/0x120 net/socket.c:661
 sock_no_sendpage+0xf5/0x140 net/core/sock.c:2686
 kernel_sendpage net/socket.c:3585 [inline]
 sock_sendpage+0xdf/0x140 net/socket.c:912
 pipe_to_sendpage+0x268/0x330 fs/splice.c:452
 splice_from_pipe_feed fs/splice.c:503 [inline]
 __splice_from_pipe+0x389/0x800 fs/splice.c:627
 splice_from_pipe fs/splice.c:662 [inline]
 generic_splice_sendpage+0xd4/0x140 fs/splice.c:833
 do_splice_from fs/splice.c:852 [inline]
 do_splice fs/splice.c:1154 [inline]
 __do_sys_splice fs/splice.c:1428 [inline]
 __se_sys_splice+0xfe7/0x16d0 fs/splice.c:1408
 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
 entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7f50c2931b29
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 11 15 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f50c28c22e8 EFLAGS: 00000246 ORIG_RAX: 0000000000000113
RAX: ffffffffffffffda RBX: 00007f50c29b9438 RCX: 00007f50c2931b29
RDX: 0000000000000005 RSI: 0000000000000000 RDI: 0000000000000003
RBP: 000000000000001e R08: 000000000004ffe6 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f50c29b9430
R13: 00007f50c29b7140 R14: 00007f50c29b943c R15: 00007f50c2987074

Crashes (13):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2022/10/23 10:34 linux-4.19.y 3f8a27f9e27b c0b80a55 .config console log report syz C [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in pipe_write
2022/06/01 11:31 linux-4.19.y 3f8a27f9e27b 3666edfe .config console log report syz C ci2-linux-4-19 INFO: task hung in pipe_write
2020/06/07 01:39 linux-4.19.y 4707d8e57273 e6b89e4e .config console log report syz ci2-linux-4-19
2022/11/23 08:17 linux-4.19.y 3f8a27f9e27b 9da37ae8 .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in pipe_write
2022/11/19 16:15 linux-4.19.y 3f8a27f9e27b 5bb70014 .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in pipe_write
2022/11/07 09:59 linux-4.19.y 3f8a27f9e27b 6d752409 .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in pipe_write
2022/10/28 16:59 linux-4.19.y 3f8a27f9e27b 8168b69e .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in pipe_write
2022/10/23 04:41 linux-4.19.y 3f8a27f9e27b c0b80a55 .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in pipe_write
2022/07/28 23:49 linux-4.19.y 3f8a27f9e27b fb95c74d .config console log report info ci2-linux-4-19 INFO: task hung in pipe_write
2022/06/01 07:24 linux-4.19.y 3f8a27f9e27b 3666edfe .config console log report info ci2-linux-4-19 INFO: task hung in pipe_write
2022/02/05 22:32 linux-4.19.y 3f8a27f9e27b a7dab638 .config console log report info ci2-linux-4-19 INFO: task hung in pipe_write
2022/01/31 07:41 linux-4.19.y 3f8a27f9e27b 495e00c5 .config console log report info ci2-linux-4-19 INFO: task hung in pipe_write
2022/01/26 13:18 linux-4.19.y 3f8a27f9e27b 2cbffd88 .config console log report info ci2-linux-4-19 INFO: task hung in pipe_write
* Struck through repros no longer work on HEAD.