INFO: task hung in pipe_write

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 9d5c0b3a8e1a Linux 4.14.295
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1016e96a880000
kernel config: https://syzkaller.appspot.com/x/.config?x=746c079015a92425
dashboard link: https://syzkaller.appspot.com/bug?extid=9f85f2f66d1766cbad33
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17e6eee2880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=141ecb7c880000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ed6fcf5895a2/disk-9d5c0b3a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/341aa3534116/vmlinux-9d5c0b3a.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+9f85f2...@syzkaller.appspotmail.com

INFO: task syz-executor285:7977 blocked for more than 140 seconds.
Not tainted 4.14.295-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor285 D28056 7977 7975 0x00000004
Call Trace:
context_switch kernel/sched/core.c:2811 [inline]
__schedule+0x88b/0x1de0 kernel/sched/core.c:3387
schedule+0x8d/0x1b0 kernel/sched/core.c:3431
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:3489
__mutex_lock_common kernel/locking/mutex.c:833 [inline]
__mutex_lock+0x669/0x1310 kernel/locking/mutex.c:893
pipe_lock_nested fs/pipe.c:82 [inline]
pipe_lock fs/pipe.c:90 [inline]
pipe_wait+0x171/0x190 fs/pipe.c:138
pipe_write+0x510/0xe10 fs/pipe.c:505
call_write_iter include/linux/fs.h:1780 [inline]
new_sync_write fs/read_write.c:469 [inline]
__vfs_write+0x44c/0x630 fs/read_write.c:482
vfs_write+0x17f/0x4d0 fs/read_write.c:544
SYSC_write fs/read_write.c:590 [inline]
SyS_write+0xf2/0x210 fs/read_write.c:582
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x7f11663f7b29
RSP: 002b:00007f11663a92f8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f116647f428 RCX: 00007f11663f7b29
RDX: 00000000fffffecc RSI: 0000000020000000 RDI: 0000000000000004
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f116647f420
R13: 00007fffa7a56e2f R14: 00007f116647f42c R15: 00007f116644d074

Showing all locks held in the system:
1 lock held by khungtaskd/1533:
#0: (tasklist_lock){.+.+}, at: [<ffffffff87024c59>] debug_show_all_locks+0x7c/0x21a kernel/locking/lockdep.c:4548
1 lock held by syz-executor285/7977:
#0: (&pipe->mutex/1){+.+.}, at: [<ffffffff8188b7b1>] pipe_lock_nested fs/pipe.c:82 [inline]
#0: (&pipe->mutex/1){+.+.}, at: [<ffffffff8188b7b1>] pipe_lock fs/pipe.c:90 [inline]
#0: (&pipe->mutex/1){+.+.}, at: [<ffffffff8188b7b1>] pipe_wait+0x171/0x190 fs/pipe.c:138

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

NMI backtrace for cpu 0
CPU: 0 PID: 1533 Comm: khungtaskd Not tainted 4.14.295-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/11/2022
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x281 lib/dump_stack.c:58
nmi_cpu_backtrace.cold+0x57/0x93 lib/nmi_backtrace.c:101
nmi_trigger_cpumask_backtrace+0x13a/0x180 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:140 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:195 [inline]
watchdog+0x5b9/0xb40 kernel/hung_task.c:274
kthread+0x30d/0x420 kernel/kthread.c:232
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:404
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 7978 Comm: syz-executor285 Not tainted 4.14.295-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/11/2022
task: ffff8880b377a0c0 task.stack: ffff8880b3348000
RIP: 0010:__orc_find+0x5b/0xf0 arch/x86/kernel/unwind_orc.c:47
RSP: 0018:ffff8880b334ef58 EFLAGS: 00000202
RAX: 000000000000000d RBX: 1ffff11016669dfb RCX: ffffffff817ec6d7
RDX: 000000000000000d RSI: ffffffff8a725fd2 RDI: ffffffff8a1947e8
RBP: ffffffff8a1947e8 R08: ffffffff8a725fd2 R09: ffffffff8a726026
R10: 000000000001e6a7 R11: 0000000000066071 R12: ffffffff8a19481c
R13: ffffffff8a1947e8 R14: ffffffff8a1947e8 R15: dffffc0000000000
FS: 00007f1166388700(0000) GS:ffff8880ba500000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fefefd9b000 CR3: 00000000b0a68000 CR4: 00000000003406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
orc_find arch/x86/kernel/unwind_orc.c:118 [inline]
unwind_next_frame+0x59a/0x17d0 arch/x86/kernel/unwind_orc.c:348
__save_stack_trace+0x90/0x160 arch/x86/kernel/stacktrace.c:44
save_stack mm/kasan/kasan.c:447 [inline]
set_track mm/kasan/kasan.c:459 [inline]
kasan_kmalloc+0xeb/0x160 mm/kasan/kasan.c:551
kmem_cache_alloc_node_trace+0x153/0x400 mm/slab.c:3661
__do_kmalloc_node mm/slab.c:3681 [inline]
__kmalloc_node_track_caller+0x38/0x70 mm/slab.c:3696
__kmalloc_reserve net/core/skbuff.c:137 [inline]
pskb_expand_head+0x128/0xd30 net/core/skbuff.c:1472
netlink_trim+0x1ae/0x220 net/netlink/af_netlink.c:1278
netlink_unicast+0x94/0x610 net/netlink/af_netlink.c:1312
ip_set_protocol+0x386/0x500 net/netfilter/ipset/ip_set_core.c:1812
nfnetlink_rcv_msg+0x9bb/0xc00 net/netfilter/nfnetlink.c:214
netlink_rcv_skb+0x125/0x390 net/netlink/af_netlink.c:2454
nfnetlink_rcv+0x1ab/0x1da0 net/netfilter/nfnetlink.c:515
netlink_unicast_kernel net/netlink/af_netlink.c:1296 [inline]
netlink_unicast+0x437/0x610 net/netlink/af_netlink.c:1322
netlink_sendmsg+0x648/0xbc0 net/netlink/af_netlink.c:1893
sock_sendmsg_nosec net/socket.c:646 [inline]
sock_sendmsg+0xb5/0x100 net/socket.c:656
sock_no_sendpage+0xe2/0x110 net/core/sock.c:2610
kernel_sendpage net/socket.c:3407 [inline]
sock_sendpage+0xdf/0x140 net/socket.c:871
pipe_to_sendpage+0x226/0x2d0 fs/splice.c:451
splice_from_pipe_feed fs/splice.c:502 [inline]
__splice_from_pipe+0x326/0x7a0 fs/splice.c:626
splice_from_pipe fs/splice.c:661 [inline]
generic_splice_sendpage+0xc1/0x110 fs/splice.c:832
do_splice_from fs/splice.c:851 [inline]
do_splice fs/splice.c:1145 [inline]
SYSC_splice fs/splice.c:1400 [inline]
SyS_splice+0xd59/0x1380 fs/splice.c:1380
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x7f11663f7b29
RSP: 002b:00007f11663882e8 EFLAGS: 00000246 ORIG_RAX: 0000000000000113
RAX: ffffffffffffffda RBX: 00007f116647f438 RCX: 00007f11663f7b29
RDX: 0000000000000005 RSI: 0000000000000000 RDI: 0000000000000003
RBP: 000000000000001e R08: 000000000004ffe6 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f116647f430
R13: 00007f116647d140 R14: 00007f116647f43c R15: 00007f116644d074
Code: fc ff df 49 89 fe 48 89 fd eb 0c 48 8d 6b 04 49 89 de 49 39 ec 72 4d 4c 89 e0 48 29 e8 48 89 c2 48 c1 e8 3f 48 c1 fa 02 48 01 d0 <48> d1 f8 48 8d 5c 85 00 48 89 d8 48 c1 e8 03 42 0f b6 14 38 48


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches