WARNING in sk_stream_kill_queues (2)

[syzbot]

Hello,

syzkaller hit the following crash on
37759fa6d0fa9e4d6036d19ac12f555bfc0aeafd
git://git.cmpxchg.org/linux-mmots.git/master
compiler: gcc (GCC) 7.1.1 20170620
.config is attached
Raw console output is attached.
C reproducer is attached
syzkaller reproducer is attached. See https://goo.gl/kgGztJ
for information about syzkaller reproducers


IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+4c37b2...@syzkaller.appspotmail.com
It will help syzbot understand when the bug is fixed. See footer for
details.
If you forward the report, please keep this part and the footer.

audit: type=1400 audit(1514626223.187:7): avc: denied { map } for
pid=3150 comm="syzkaller691304" path="/root/syzkaller691304410" dev="sda1"
ino=16481 scontext=unconfined_u:system_r:insmod_t:s0-s0:c0.c1023
tcontext=unconfined_u:object_r:user_home_t:s0 tclass=file permissive=1
device lo entered promiscuous mode
WARNING: CPU: 0 PID: 3151 at net/core/stream.c:206
sk_stream_kill_queues+0x3c5/0x520 net/core/stream.c:206
Kernel panic - not syncing: panic_on_warn set ...

CPU: 0 PID: 3151 Comm: syzkaller691304 Not tainted 4.15.0-rc4-mm1+ #49
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x194/0x257 lib/dump_stack.c:53
panic+0x1e4/0x41c kernel/panic.c:183
__warn+0x1dc/0x200 kernel/panic.c:547
report_bug+0x211/0x2d0 lib/bug.c:184
fixup_bug.part.11+0x37/0x80 arch/x86/kernel/traps.c:177
fixup_bug arch/x86/kernel/traps.c:246 [inline]
do_error_trap+0x2d7/0x3e0 arch/x86/kernel/traps.c:295
do_invalid_op+0x1b/0x20 arch/x86/kernel/traps.c:314
invalid_op+0x22/0x40 arch/x86/entry/entry_64.S:1079
RIP: 0010:sk_stream_kill_queues+0x3c5/0x520 net/core/stream.c:206
RSP: 0018:ffff8801c8fd7238 EFLAGS: 00010293
RAX: ffff8801ccb6c4c0 RBX: ffff8801ccc74040 RCX: ffffffff842cae35
RDX: 0000000000000000 RSI: ffffffff86540c60 RDI: ffff8801ccc74278
RBP: ffff8801c8fd7278 R08: 1ffff100391fadd6 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000b00
R13: ffff8801ccc74230 R14: ffffffff88449ac0 R15: ffff8801ccc74178
inet_csk_destroy_sock+0x175/0x3f0 net/ipv4/inet_connection_sock.c:834
tcp_done+0x1e9/0x240 net/ipv4/tcp.c:3489
tcp_time_wait+0x60b/0xa60 net/ipv4/tcp_minisocks.c:333
tcp_rcv_state_process+0x34b0/0x4830 net/ipv4/tcp_input.c:5988
tcp_v6_do_rcv+0x739/0x11b0 net/ipv6/tcp_ipv6.c:1331
sk_backlog_rcv include/net/sock.h:907 [inline]
__release_sock+0x124/0x360 net/core/sock.c:2274
release_sock+0xa4/0x2a0 net/core/sock.c:2789
tcp_close+0x57c/0xfc0 net/ipv4/tcp.c:2241
tls_sk_proto_close+0x4f8/0x800 net/tls/tls_main.c:260
inet_release+0xed/0x1c0 net/ipv4/af_inet.c:427
inet6_release+0x50/0x70 net/ipv6/af_inet6.c:433
sock_release+0x8d/0x1e0 net/socket.c:593
sock_close+0x16/0x20 net/socket.c:1121
__fput+0x327/0x7e0 fs/file_table.c:209
____fput+0x15/0x20 fs/file_table.c:243
task_work_run+0x199/0x270 kernel/task_work.c:113
exit_task_work include/linux/task_work.h:22 [inline]
do_exit+0x9bb/0x1ad0 kernel/exit.c:869
do_group_exit+0x149/0x400 kernel/exit.c:972
SYSC_exit_group kernel/exit.c:983 [inline]
SyS_exit_group+0x1d/0x20 kernel/exit.c:981
entry_SYSCALL_64_fastpath+0x1f/0x96
RIP: 0033:0x440839
RSP: 002b:00007fffb9900138 EFLAGS: 00000202 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0100000000000000 RCX: 0000000000440839
RDX: 0000000000440839 RSI: 000000002003b000 RDI: 0000000000000000
RBP: 00000000006cb018 R08: 000000000000001c R09: 00000000004002c8
R10: 000000000000001c R11: 0000000000000202 R12: 0000000000000000
R13: 0000000000401d70 R14: 0000000000000000 R15: 0000000000000000
Dumping ftrace buffer:
(ftrace buffer empty)
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
This bug is generated by a dumb bot. It may contain errors.
See https://goo.gl/tpsmEJ for details.
Direct all questions to syzk...@googlegroups.com.

syzbot will keep track of this bug report.
If you forgot to add the Reported-by tag, once the fix for this bug is
merged
into any tree, please reply to this email with:
#syz fix: exact-commit-title
If you want to test a patch for this bug, please reply with:
#syz test: git://repo/address.git branch
and provide the patch inline or as an attachment.
To mark this as a duplicate of another syzbot report, please reply with:
#syz dup: exact-subject-of-another-report
If it's a one-off invalid bug report, please reply with:
#syz invalid
Note: if the crash happens again, it will cause creation of a new bug
report.
Note: all commands must start from beginning of the line in the email body.

[Cong Wang]

#syz dup: KASAN: slab-out-of-bounds Write in tcp_v6_syn_recv_sock