From: syzbot <syzbot+ee1fdd8dcc770a3a169a@syzkaller.appspotmail.com>
To: Liam.Howlett@Oracle.com, akpm@linux-foundation.org,
arnd@arndb.de, ccross@google.com, david@redhat.com,
ebiederm@xmission.com, liam.howlett@oracle.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
michel@lespinasse.org, syzkaller-bugs@googlegroups.com,
vbabka@suse.cz, willy@infradead.org
Subject: Re: [syzbot] general protection fault in vma_interval_tree_remove
Date: Sat, 14 May 2022 17:09:10 -0700 [thread overview]
Message-ID: <0000000000007fa7ff05df01b7c4@google.com> (raw)
In-Reply-To: <0000000000007f31db05de0638f0@google.com>
syzbot has bisected this issue to:
commit b7d0f898f5ce328ad809417f2e728b58153d52d1
Author: Liam R. Howlett <Liam.Howlett@Oracle.com>
Date: Fri May 13 04:15:44 2022 +0000
mm: remove the vma linked list
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12fefe69f00000
start commit: 1e1b28b936ae Add linux-next specific files for 20220513
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=11fefe69f00000
console output: https://syzkaller.appspot.com/x/log.txt?x=16fefe69f00000
kernel config: https://syzkaller.appspot.com/x/.config?x=e4eb3c0c4b289571
dashboard link: https://syzkaller.appspot.com/bug?extid=ee1fdd8dcc770a3a169a
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=142757f1f00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17cf0966f00000
Reported-by: syzbot+ee1fdd8dcc770a3a169a@syzkaller.appspotmail.com
Fixes: b7d0f898f5ce ("mm: remove the vma linked list")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2022-05-15 0:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 12:06 [syzbot] general protection fault in vma_interval_tree_remove syzbot
2022-05-14 20:18 ` syzbot
2022-05-14 20:50 ` Andrew Morton
2022-05-16 18:00 ` Liam Howlett
2022-05-19 2:03 ` Liam Howlett
2022-05-19 5:18 ` Dmitry Vyukov
2022-05-15 0:09 ` 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=0000000000007fa7ff05df01b7c4@google.com \
--to=syzbot+ee1fdd8dcc770a3a169a@syzkaller.appspotmail.com \
--cc=Liam.Howlett@Oracle.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=ccross@google.com \
--cc=david@redhat.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=michel@lespinasse.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
/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).