From: syzbot <syzbot+7728e4ab5371cebc9c00@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, andreyknvl@google.com,
liam.howlett@oracle.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, peterx@redhat.com, quic_qiancai@quicinc.com,
syzkaller-bugs@googlegroups.com, torvalds@linux-foundation.org
Subject: Re: [syzbot] WARNING in vma_merge
Date: Wed, 27 Apr 2022 21:06:12 -0700 [thread overview]
Message-ID: <000000000000e6000105ddaf0b55@google.com> (raw)
In-Reply-To: <000000000000a23c8505dda227eb@google.com>
syzbot has bisected this issue to:
commit 80207910cd71b4e0e87140d165d82b5d3ff69e53
Author: Andrey Konovalov <andreyknvl@google.com>
Date: Fri Mar 25 01:13:12 2022 +0000
kasan: move and hide kasan_save_enable/restore_multi_shot
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16d9a4e4f00000
start commit: f02ac5c95dfd Add linux-next specific files for 20220427
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=15d9a4e4f00000
console output: https://syzkaller.appspot.com/x/log.txt?x=11d9a4e4f00000
kernel config: https://syzkaller.appspot.com/x/.config?x=e9256c70f586da8a
dashboard link: https://syzkaller.appspot.com/bug?extid=7728e4ab5371cebc9c00
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15f76f82f00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12b42c3cf00000
Reported-by: syzbot+7728e4ab5371cebc9c00@syzkaller.appspotmail.com
Fixes: 80207910cd71 ("kasan: move and hide kasan_save_enable/restore_multi_shot")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2022-04-28 4:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 12:43 [syzbot] WARNING in vma_merge syzbot
2022-04-27 13:15 ` syzbot
2022-04-27 17:20 ` Andrew Morton
2022-04-27 17:52 ` Liam Howlett
2022-04-27 19:06 ` Liam Howlett
2022-04-28 5:13 ` Dmitry Vyukov
2022-04-28 4:06 ` 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=000000000000e6000105ddaf0b55@google.com \
--to=syzbot+7728e4ab5371cebc9c00@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@google.com \
--cc=liam.howlett@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peterx@redhat.com \
--cc=quic_qiancai@quicinc.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.