BUG: unable to handle kernel paging request in __put_user_4

[syzbot]

Hello,

syzkaller hit the following crash on
a4f586bceda49b0e43a3606905582e5104052e4b
git://git.cmpxchg.org/linux-mmots.git/master
compiler: gcc (GCC) 7.1.1 20170620
.config is attached
Raw console output is attached.

Unfortunately, I don't have any reproducer for this bug yet.
CC: [ak...@linux-foundation.org dst...@suse.com gre...@linuxfoundation.org
horms+...@verge.net.au kees...@chromium.org
linux-...@vger.kernel.org li...@roeck-us.net lu...@amacapital.net
marcos.s...@gmail.com mi...@kernel.org ol...@redhat.com
tg...@linutronix.de w...@chromium.org]

reason=80000021 qualification=0000000000000000
IDTVectoring: info=00000000 errcode=00000000
TSC Offset = 0xffffffe170f077a9
TPR Threshold = 0x00
EPT pointer = 0x00000001c093001e
BUG: unable to handle kernel paging request at fffffffffffffff8
IP: __put_user_4+0x1e/0x30 arch/x86/lib/putuser.S:70
PGD 5e28067 P4D 5e28067 PUD 5e2a067 PMD 0
Oops: 0002 [#1] SMP KASAN
Dumping ftrace buffer:
(ftrace buffer empty)
Modules linked in:
CPU: 1 PID: 5865 Comm: syz-executor0 Not tainted 4.15.0-rc1-mm1+ #28
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
task: ffff8801d8f70440 task.stack: ffff8801c1f30000
RIP: 0010:__put_user_4+0x1e/0x30 arch/x86/lib/putuser.S:70
RSP: 0018:ffff8801c1f37b30 EFLAGS: 00010297
RAX: 0000000000000107 RBX: 00007fffffffeffd RCX: 0000000020000000
RDX: 0000000000006cf7 RSI: ffffc900017ce000 RDI: 0000000000000282
RBP: ffff8801c1f37dc8 R08: ffff8801db51f740 R09: 1ffff100383e6f3b
R10: ffff8801d8f70440 R11: 0000000000000000 R12: 000000002918cb00
R13: ffff8801d8c8e140 R14: 0000000000000000 R15: 0000000000000107
FS: 00007f144a1f3700(0000) GS:ffff8801db500000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: fffffffffffffff8 CR3: 00000001d8146000 CR4: 00000000001426e0
DR0: 0000000020000000 DR1: 0000000020000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff1 DR7: 00000000000b0602
Call Trace:
SYSC_clone kernel/fork.c:2209 [inline]
SyS_clone+0x37/0x50 kernel/fork.c:2203
do_syscall_64+0x26c/0x920 arch/x86/entry/common.c:285
entry_SYSCALL64_slow_path+0x25/0x25
RIP: 0033:0x4529d9
RSP: 002b:00007f144a1f2c58 EFLAGS: 00000212 ORIG_RAX: 0000000000000038
RAX: ffffffffffffffda RBX: 0000000000758020 RCX: 00000000004529d9
RDX: 0000000020000000 RSI: 0000000020cc3000 RDI: 000000002918cb00
RBP: 0000000000000047 R08: 0000000020543fe4 R09: 0000000000000000
R10: 0000000020000000 R11: 0000000000000212 R12: 00000000006ed748
R13: 00000000ffffffff R14: 00007f144a1f36d4 R15: 0000000000000000
Code: 00 c3 90 66 2e 0f 1f 84 00 00 00 00 00 65 48 8b 1c 25 40 65 01 00 48
8b 9b a0 15 00 00 48 83 eb 03 48 39 d9 73 3c 0f 1f 00 89 01 <31> c0 0f 1f
00 c3 66 90 66 2e 0f 1f 84 00 00 00 00 00 65 48 8b
RIP: __put_user_4+0x1e/0x30 arch/x86/lib/putuser.S:70 RSP: ffff8801c1f37b30
CR2: fffffffffffffff8
---[ end trace 6f61ff2c5ff37107 ]---
Kernel panic - not syncing: Fatal exception
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.
Please credit me with: Reported-by: syzbot <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.
Note: all commands must start from beginning of the line in the email body.
To upstream this report, please reply with:
#syz upstream

[Dmitry Vyukov]

looks like problem is somewhere else

#syz invalid

On Sun, Dec 3, 2017 at 2:22 PM, syzbot
<bot+275b81cca708bc4609...@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/f40304381824a9379a055f6f7c71%40google.com.
> For more options, visit https://groups.google.com/d/optout.