WARNING in sk_stream_kill_queues

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 1e61bd26fa2c Linux 4.14.306
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16097db4c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=1411e822b6d22b39
dashboard link: https://syzkaller.appspot.com/bug?extid=ac677d2e23a3b4ed5637
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/625245171cd5/disk-1e61bd26.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9facd1f0ea57/vmlinux-1e61bd26.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f2f80facb3a7/bzImage-1e61bd26.xz

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

device team_slave_1 left promiscuous mode
device team0 left promiscuous mode
device team_slave_0 left promiscuous mode
device team_slave_1 left promiscuous mode
------------[ cut here ]------------
WARNING: CPU: 1 PID: 12618 at net/core/stream.c:212 sk_stream_kill_queues+0x2a3/0x380 net/core/stream.c:212
Kernel panic - not syncing: kernel: panic_on_warn set ...

CPU: 1 PID: 12618 Comm: syz-executor.4 Not tainted 4.14.306-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/21/2023
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x281 lib/dump_stack.c:58
panic+0x21d/0x451 kernel/panic.c:247
check_panic_on_warn.cold+0x19/0x35 kernel/panic.c:171
__warn+0xdf/0x1e0 kernel/panic.c:603
report_bug+0x208/0x250 lib/bug.c:183
fixup_bug arch/x86/kernel/traps.c:177 [inline]
fixup_bug arch/x86/kernel/traps.c:172 [inline]
do_error_trap+0x195/0x2d0 arch/x86/kernel/traps.c:295
invalid_op+0x1b/0x40 arch/x86/entry/entry_64.S:967
RIP: 0010:sk_stream_kill_queues+0x2a3/0x380 net/core/stream.c:212
RSP: 0018:ffff8880a98af718 EFLAGS: 00010297
RAX: ffff88809a8fe3c0 RBX: ffff88809ef26040 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffff88809a8fec70 RDI: ffff88809ef26278
RBP: 0000000000000b00 R08: ffffffff8ba6da1c R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: ffff88809ef26230
R13: ffffffff8c9b7760 R14: ffffed1013de4c3b R15: ffff88809ef261d8
inet_csk_destroy_sock+0x171/0x400 net/ipv4/inet_connection_sock.c:868
tcp_done+0x1b8/0x210 net/ipv4/tcp.c:3436
tcp_rcv_state_process+0x1f0a/0x4af0 net/ipv4/tcp_input.c:6155
tcp_v6_do_rcv+0x3d5/0x13e0 net/ipv6/tcp_ipv6.c:1361
sk_backlog_rcv include/net/sock.h:923 [inline]
__release_sock+0x12a/0x350 net/core/sock.c:2284
tcp_close+0x548/0xed0 net/ipv4/tcp.c:2238
inet_release+0xdf/0x1b0 net/ipv4/af_inet.c:425
inet6_release+0x4c/0x70 net/ipv6/af_inet6.c:450
__sock_release+0xcd/0x2b0 net/socket.c:602
audit: type=1800 audit(1677070752.269:56): pid=12646 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.4" name="bus" dev="sda1" ino=14251 res=0
sock_close+0x15/0x20 net/socket.c:1139
__fput+0x25f/0x7a0 fs/file_table.c:210
task_work_run+0x11f/0x190 kernel/task_work.c:113
exit_task_work include/linux/task_work.h:22 [inline]
do_exit+0xa44/0x2850 kernel/exit.c:915
do_group_exit+0x100/0x2e0 kernel/exit.c:1037
get_signal+0x38d/0x1ca0 kernel/signal.c:2412
do_signal+0x7c/0x1550 arch/x86/kernel/signal.c:792
exit_to_usermode_loop+0x160/0x200 arch/x86/entry/common.c:160
prepare_exit_to_usermode+0x1af/0x210 arch/x86/entry/common.c:199
retint_user+0x8/0x18
RIP: 0033:0x7fcdd5304101
RSP: 002b:00000000200000e0 EFLAGS: 00010217
RAX: 0000000000000000 RBX: 00007fcdd5424050 RCX: 00007fcdd53040f9
RDX: 0000000020000380 RSI: 00000000200000e0 RDI: 0000000000002000
RBP: 00007fcdd535fae9 R08: 0000000020000440 R09: 0000000020000440
R10: 0000000020000400 R11: 0000000000000206 R12: 0000000000000000
R13: 00007fff888fc44f R14: 00007fcdd3855300 R15: 0000000000022000
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
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]

syzbot has found a reproducer for the following issue on:

HEAD commit: 1e61bd26fa2c Linux 4.14.306
git tree: linux-4.14.y

console output: https://syzkaller.appspot.com/x/log.txt?x=14921d44c80000

kernel config: https://syzkaller.appspot.com/x/.config?x=1411e822b6d22b39
dashboard link: https://syzkaller.appspot.com/bug?extid=ac677d2e23a3b4ed5637
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16edbed8c80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=106909f7480000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/625245171cd5/disk-1e61bd26.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9facd1f0ea57/vmlinux-1e61bd26.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f2f80facb3a7/bzImage-1e61bd26.xz

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 7974 at net/core/stream.c:212 sk_stream_kill_queues+0x2a3/0x380 net/core/stream.c:212

Kernel panic - not syncing: kernel: panic_on_warn set ...

CPU: 1 PID: 7974 Comm: syz-executor487 Not tainted 4.14.306-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/21/2023
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x281 lib/dump_stack.c:58
panic+0x21d/0x451 kernel/panic.c:247
check_panic_on_warn.cold+0x19/0x35 kernel/panic.c:171
__warn+0xdf/0x1e0 kernel/panic.c:603
report_bug+0x208/0x250 lib/bug.c:183
fixup_bug arch/x86/kernel/traps.c:177 [inline]
fixup_bug arch/x86/kernel/traps.c:172 [inline]
do_error_trap+0x195/0x2d0 arch/x86/kernel/traps.c:295
invalid_op+0x1b/0x40 arch/x86/entry/entry_64.S:967
RIP: 0010:sk_stream_kill_queues+0x2a3/0x380 net/core/stream.c:212

RSP: 0018:ffff8880984df990 EFLAGS: 00010297
RAX: ffff8880b32b4540 RBX: ffff88809d85e040 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffff8880b32b4df0 RDI: ffff88809d85e278
RBP: 0000000000000b00 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: ffff88809d85e230
R13: ffffffff8c9b7760 R14: ffffed1013b0bc3b R15: ffff88809d85e1d8

inet_csk_destroy_sock+0x171/0x400 net/ipv4/inet_connection_sock.c:868
tcp_done+0x1b8/0x210 net/ipv4/tcp.c:3436
tcp_rcv_state_process+0x1f0a/0x4af0 net/ipv4/tcp_input.c:6155
tcp_v6_do_rcv+0x3d5/0x13e0 net/ipv6/tcp_ipv6.c:1361
sk_backlog_rcv include/net/sock.h:923 [inline]
__release_sock+0x12a/0x350 net/core/sock.c:2284
tcp_close+0x548/0xed0 net/ipv4/tcp.c:2238
inet_release+0xdf/0x1b0 net/ipv4/af_inet.c:425
inet6_release+0x4c/0x70 net/ipv6/af_inet6.c:450
__sock_release+0xcd/0x2b0 net/socket.c:602

sock_close+0x15/0x20 net/socket.c:1139
__fput+0x25f/0x7a0 fs/file_table.c:210
task_work_run+0x11f/0x190 kernel/task_work.c:113
exit_task_work include/linux/task_work.h:22 [inline]
do_exit+0xa44/0x2850 kernel/exit.c:915
do_group_exit+0x100/0x2e0 kernel/exit.c:1037

SYSC_exit_group kernel/exit.c:1048 [inline]
SyS_exit_group+0x19/0x20 kernel/exit.c:1046
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x5e/0xd3
RIP: 0033:0x7f9a365aea79
RSP: 002b:00007ffedf036688 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 00007f9a36622330 RCX: 00007f9a365aea79
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffffffffffc0 R09: 000000000000001c
R10: 0000000020000008 R11: 0000000000000246 R12: 00007f9a36622330
R13: 0000000000000001 R14: 0000000000000000 R15: 0000000000000001