kernel BUG at ./include/linux/mm.h:LINE!

[syzbot]

Hello,

syzkaller hit the following crash on
5d51332f20b270812376cf8751987e283f30de4a
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master
compiler: gcc (GCC) 7.1.1 20170620
.config is attached
Raw console output is attached.


CC: [da...@davemloft.net kuz...@ms2.inr.ac.ru yosh...@linux-ipv6.org
net...@vger.kernel.org linux-...@vger.kernel.org]

------------[ cut here ]------------
kernel BUG at ./include/linux/mm.h:466!
invalid opcode: 0000 [#1] SMP KASAN
Dumping ftrace buffer:
(ftrace buffer empty)
Modules linked in:
CPU: 1 PID: 9689 Comm: syz-executor1 Not tainted 4.13.0-rc5-next-20170816+
#4
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011
task: ffff880030c86080 task.stack: ffff88003b700000
RIP: 0010:put_page_testzero include/linux/mm.h:466 [inline]
RIP: 0010:page_frag_free+0x1ca/0x290 mm/page_alloc.c:4367
RSP: 0018:ffff88003b706848 EFLAGS: 00010203
RAX: 0000000000000000 RBX: ffffea0000dd1d00 RCX: 0000000000000000
RDX: 0000000000002695 RSI: ffffffff81940a54 RDI: ffffed00076e0cf8
RBP: ffff88003b706910 R08: 0000000000000000 R09: 1ffff100076e0c27
R10: dffffc0000000000 R11: ffffffff85b2d438 R12: 1ffff100076e0d09
R13: 1ffff100076e0d0d R14: ffff88003b7068e8 R15: 0000000000000000
FS: 00007f2fa4102700(0000) GS:ffff88003ed00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000002001af48 CR3: 000000004c099000 CR4: 00000000000006e0
DR0: 0000000020000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600
Call Trace:
skb_free_frag include/linux/skbuff.h:2625 [inline]
skb_free_head+0x8b/0xb0 net/core/skbuff.c:552
skb_release_data+0x58c/0x790 net/core/skbuff.c:574
skb_release_all+0x4a/0x60 net/core/skbuff.c:631
__kfree_skb net/core/skbuff.c:645 [inline]
kfree_skb+0x15d/0x4c0 net/core/skbuff.c:663
ip_frag_queue net/ipv4/ip_fragment.c:474 [inline]
ip_defrag+0xc69/0x4000 net/ipv4/ip_fragment.c:680
ip_local_deliver+0x174/0x6d0 net/ipv4/ip_input.c:253
dst_input include/net/dst.h:477 [inline]
ip_rcv_finish+0x8db/0x19c0 net/ipv4/ip_input.c:397
NF_HOOK include/linux/netfilter.h:248 [inline]
ip_rcv+0xc3f/0x17d0 net/ipv4/ip_input.c:488
__netif_receive_skb_core+0x19af/0x33d0 net/core/dev.c:4418
__netif_receive_skb+0x2c/0x1b0 net/core/dev.c:4456
netif_receive_skb_internal+0x10b/0x5e0 net/core/dev.c:4527
netif_receive_skb+0xae/0x390 net/core/dev.c:4551
tun_rx_batched.isra.43+0x5e7/0x860 drivers/net/tun.c:1221
tun_get_user+0x11dd/0x2150 drivers/net/tun.c:1542
tun_chr_write_iter+0xd8/0x190 drivers/net/tun.c:1568
call_write_iter include/linux/fs.h:1742 [inline]
new_sync_write fs/read_write.c:457 [inline]
__vfs_write+0x684/0x970 fs/read_write.c:470
vfs_write+0x189/0x510 fs/read_write.c:518
SYSC_write fs/read_write.c:565 [inline]
SyS_write+0xef/0x220 fs/read_write.c:557
entry_SYSCALL_64_fastpath+0x1f/0xbe
RIP: 0033:0x40bab1
RSP: 002b:00007f2fa4101c00 EFLAGS: 00000293 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00000000000000b8 RCX: 000000000040bab1
RDX: 00000000000000b8 RSI: 000000002001af48 RDI: 0000000000000015
RBP: 0000000000708000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000293 R12: 00000000ffffffff
R13: 00000000000037d0 R14: 00000000006e5890 R15: 0000000000001000
Code: 00 42 c7 44 20 10 00 00 00 00 48 81 c4 a0 00 00 00 5b 41 5c 41 5d 41
5e 41 5f 5d c3 48 c7 c6 40 02 ef 84 48 89 df e8 86 77 0c 00 <0f> 0b 48 89
da 48 c1 ea 03 80 3c 02 00 0f 85 8f 00 00 00 48 8b
RIP: put_page_testzero include/linux/mm.h:466 [inline] RSP: ffff88003b706848
RIP: page_frag_free+0x1ca/0x290 mm/page_alloc.c:4367 RSP: ffff88003b706848
---[ end trace 167c4acffde04cf4 ]---


---
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.
Once a fix for this bug is committed, please reply to this email with:
#syz fix: exact-commit-title
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.
To upstream this report, please reply with:
#syz upstream

[Dmitry Vyukov]

This happened only 3 times, last time on Aug 29, no repro. Let's close
this for now. At least we need a fresh report.

#syz invalid


On Fri, Oct 27, 2017 at 9:24 AM, syzbot
<bot+18132812a54b1c064d...@syzkaller.appspotmail.com>
wrote:

> --
> You received this message because you are subscribed to the Google Groups
> "syzkaller-upstream-moderation" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to syzkaller-upstream-m...@googlegroups.com.
> To post to this group, send email to
> syzkaller-upst...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/syzkaller-upstream-moderation/089e0825d4245d58c3055c822c61%40google.com.
> For more options, visit https://groups.google.com/d/optout.