From: syzbot <syzbot+8847ae8c7bc46bc9c10e@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, dhowells@redhat.com,
linmiaohe@huawei.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, surenb@google.com,
syzkaller-bugs@googlegroups.com, vbabka@suse.cz,
willy@infradead.org
Subject: Re: [syzbot] KASAN: stack-out-of-bounds Write in check_move_unevictable_pages
Date: Tue, 07 Jun 2022 13:48:17 -0700 [thread overview]
Message-ID: <0000000000004bcf6905e0e1b527@google.com> (raw)
In-Reply-To: <0000000000003fc46005e0db5390@google.com>
syzbot has bisected this issue to:
commit 15603c238d1318c66c49df232fb2e2631a0062a0
Author: Matthew Wilcox (Oracle) <willy@infradead.org>
Date: Sat Jun 4 21:39:09 2022 +0000
vmscan: Add check_move_unevictable_folios()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11ad0107f00000
start commit: 73d0e32571a0 Add linux-next specific files for 20220607
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=13ad0107f00000
console output: https://syzkaller.appspot.com/x/log.txt?x=15ad0107f00000
kernel config: https://syzkaller.appspot.com/x/.config?x=448ee2b64e828049
dashboard link: https://syzkaller.appspot.com/bug?extid=8847ae8c7bc46bc9c10e
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14359627f00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=177d5f3ff00000
Reported-by: syzbot+8847ae8c7bc46bc9c10e@syzkaller.appspotmail.com
Fixes: 15603c238d13 ("vmscan: Add check_move_unevictable_folios()")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2022-06-07 20:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 13:11 syzbot
2022-06-07 16:24 ` syzbot
2022-06-07 19:27 ` Matthew Wilcox
2022-06-07 20:48 ` 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=0000000000004bcf6905e0e1b527@google.com \
--to=syzbot+8847ae8c7bc46bc9c10e@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=surenb@google.com \
--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