From: Andrew Morton <akpm@linux-foundation.org>
To: syzbot <syzbot+120abb1c3f7bfdc523f7@syzkaller.appspotmail.com>
Cc: jglisse@redhat.com, kirill.shutemov@linux.intel.com,
ldufour@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, mhocko@suse.com, minchan@kernel.org,
ross.zwisler@linux.intel.com, sfr@canb.auug.org.au,
syzkaller-bugs@googlegroups.com, ying.huang@intel.com
Subject: Re: general protection fault in _vm_normal_page
Date: Wed, 11 Jul 2018 14:04:49 -0700 [thread overview]
Message-ID: <20180711140449.3702358d7e8898017e34dcfd@linux-foundation.org> (raw)
In-Reply-To: <00000000000010c9390570bc0643@google.com>
On Wed, 11 Jul 2018 09:49:01 -0700 syzbot <syzbot+120abb1c3f7bfdc523f7@syzkaller.appspotmail.com> wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit: 98be45067040 Add linux-next specific files for 20180711
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=12496ac2400000
> kernel config: https://syzkaller.appspot.com/x/.config?x=3f3b3673fec35d01
> dashboard link: https://syzkaller.appspot.com/bug?extid=120abb1c3f7bfdc523f7
> compiler: gcc (GCC) 8.0.1 20180413 (experimental)
> syzkaller repro:https://syzkaller.appspot.com/x/repro.syz?x=12a46568400000
Handy. /dev/ion from drivers/staging/android/ion/ion.c
>
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by: syzbot+120abb1c3f7bfdc523f7@syzkaller.appspotmail.com
>
> R10: 0000000004000812 R11: 0000000000000246 R12: 0000000000000005
> R13: 00000000004c0565 R14: 00000000004cffb0 R15: 0000000000000005
> ion_mmap: failure mapping buffer to userspace
> kasan: CONFIG_KASAN_INLINE enabled
> kasan: GPF could be caused by NULL-ptr deref or user memory access
> general protection fault: 0000 [#1] SMP KASAN
> CPU: 0 PID: 4785 Comm: syz-executor0 Not tainted 4.18.0-rc4-next-20180711+
> #4
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
> Google 01/01/2011
> RIP: 0010:_vm_normal_page+0x1e5/0x330 mm/memory.c:828
Presumably has a NULL vma->vm_ops. Probably one of the now-removed
checks in mm-drop-unneeded-vm_ops-checks.patch would have avoided
this.
Something for Kirill to think about ;)
next prev parent reply other threads:[~2018-07-11 21:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-11 16:49 general protection fault in _vm_normal_page syzbot
2018-07-11 21:04 ` Andrew Morton [this message]
2018-07-12 14:31 ` Kirill A. Shutemov
2019-04-01 1:36 ` syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180711140449.3702358d7e8898017e34dcfd@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jglisse@redhat.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=ldufour@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=minchan@kernel.org \
--cc=ross.zwisler@linux.intel.com \
--cc=sfr@canb.auug.org.au \
--cc=syzbot+120abb1c3f7bfdc523f7@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=ying.huang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).