From: syzbot <syzbot+120abb1c3f7bfdc523f7@syzkaller.appspotmail.com>
To: aarcange@redhat.com, akpm@linux-foundation.org,
dave.hansen@linux.intel.com, dvyukov@google.com,
dwmw@amazon.co.uk, jglisse@redhat.com,
kirill.shutemov@linux.intel.com, kirill@shutemov.name,
ldufour@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux@dominikbrodowski.net, mhocko@suse.com,
minchan@kernel.org, oleg@redhat.com, rientjes@google.com,
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: Sun, 31 Mar 2019 18:36:01 -0700 [thread overview]
Message-ID: <0000000000000531f105856e0b18@google.com> (raw)
In-Reply-To: <00000000000010c9390570bc0643@google.com>
syzbot has bisected this bug to:
commit 4a110365f1da9d5cabbd0a01796027c0a6d5e80b
Author: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
Date: Wed Jul 11 00:45:42 2018 +0000
mm: drop unneeded ->vm_ops checks
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10b0650f200000
start commit: 98be4506 Add linux-next specific files for 20180711
git tree: linux-next
final crash: https://syzkaller.appspot.com/x/report.txt?x=12b0650f200000
console output: https://syzkaller.appspot.com/x/log.txt?x=14b0650f200000
kernel config: https://syzkaller.appspot.com/x/.config?x=3f3b3673fec35d01
dashboard link: https://syzkaller.appspot.com/bug?extid=120abb1c3f7bfdc523f7
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12a46568400000
Reported-by: syzbot+120abb1c3f7bfdc523f7@syzkaller.appspotmail.com
Fixes: 4a110365f1da ("mm: drop unneeded ->vm_ops checks")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2019-04-01 1:36 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
2018-07-12 14:31 ` Kirill A. Shutemov
2019-04-01 1:36 ` syzbot [this message]
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=0000000000000531f105856e0b18@google.com \
--to=syzbot+120abb1c3f7bfdc523f7@syzkaller.appspotmail.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@linux.intel.com \
--cc=dvyukov@google.com \
--cc=dwmw@amazon.co.uk \
--cc=jglisse@redhat.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=kirill@shutemov.name \
--cc=ldufour@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@dominikbrodowski.net \
--cc=mhocko@suse.com \
--cc=minchan@kernel.org \
--cc=oleg@redhat.com \
--cc=rientjes@google.com \
--cc=ross.zwisler@linux.intel.com \
--cc=sfr@canb.auug.org.au \
--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).