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

[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+f9831b...@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.

------------[ cut here ]------------
kernel BUG at ./include/linux/mm.h:844!
invalid opcode: 0000 [#1] SMP KASAN
Dumping ftrace buffer:
(ftrace buffer empty)
Modules linked in:
CPU: 1 PID: 3152 Comm: syzkaller757651 Not tainted 4.15.0-rc4-mm1+ #49
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:get_page include/linux/mm.h:844 [inline]
RIP: 0010:mon_bin_vma_fault+0x2f4/0x400 drivers/usb/mon/mon_bin.c:1239
RSP: 0018:ffff8801cb0af510 EFLAGS: 00010203
RAX: 0000000000000000 RBX: 1ffff10039615ea4 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 1ffff10039615dee RDI: ffffed0039615e90
RBP: ffff8801cb0af5e8 R08: 1ffff10039615db0 R09: 0000000000000000
R10: dffffc0000000000 R11: 0000000000000000 R12: 1ffff10039615ea8
R13: dffffc0000000000 R14: ffff8801cb0af840 R15: ffffea000723fc00
FS: 00007f49b1386700(0000) GS:ffff8801db300000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055cfb39ce0b8 CR3: 00000001ccb19003 CR4: 00000000001606e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__do_fault+0xeb/0x30f mm/memory.c:3206
do_read_fault mm/memory.c:3616 [inline]
do_fault mm/memory.c:3716 [inline]
handle_pte_fault mm/memory.c:3947 [inline]
__handle_mm_fault+0x1d8f/0x3ce0 mm/memory.c:4071
handle_mm_fault+0x38f/0x930 mm/memory.c:4108
faultin_page mm/gup.c:502 [inline]
__get_user_pages+0x50c/0x15f0 mm/gup.c:699
populate_vma_page_range+0x20e/0x2f0 mm/gup.c:1200
__mm_populate+0x23a/0x450 mm/gup.c:1250
mm_populate include/linux/mm.h:2233 [inline]
vm_mmap_pgoff+0x241/0x280 mm/util.c:338
SYSC_mmap_pgoff mm/mmap.c:1544 [inline]
SyS_mmap_pgoff+0x462/0x5f0 mm/mmap.c:1502
SYSC_mmap arch/x86/kernel/sys_x86_64.c:100 [inline]
SyS_mmap+0x16/0x20 arch/x86/kernel/sys_x86_64.c:91
entry_SYSCALL_64_fastpath+0x1f/0x96
RIP: 0033:0x449249
RSP: 002b:00007f49b1385d98 EFLAGS: 00000212 ORIG_RAX: 0000000000000009
RAX: ffffffffffffffda RBX: 00000000006dac24 RCX: 0000000000449249
RDX: 0000000001000004 RSI: 0000000000004000 RDI: 0000000020ac6000
RBP: 0000000000000000 R08: 000000000000000b R09: 0000000000000000
R10: 0000000000008011 R11: 0000000000000212 R12: 00000000006dac20
R13: 6273752f7665642f R14: 00007f49b13869c0 R15: 0000000000000005
Code: 00 44 89 e0 5b 41 5c 41 5d 41 5e 41 5f 5d c3 41 bc 02 00 00 00 eb bb
e8 db e1 96 fd 48 c7 c6 80 1f d1 85 4c 89 ff e8 6c a3 c0 fd <0f> 0b 48 89
95 28 ff ff ff 48 89 85 30 ff ff ff e8 b7 e1 96 fd
RIP: get_page include/linux/mm.h:844 [inline] RSP: ffff8801cb0af510
RIP: mon_bin_vma_fault+0x2f4/0x400 drivers/usb/mon/mon_bin.c:1239 RSP:
ffff8801cb0af510
---[ end trace 8ea221790b36af86 ]---


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