From: syzbot <syzbot+4d875b4d2e2b60bae9b4@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, shy828301@gmail.com,
syzkaller-bugs@googlegroups.com, willy@infradead.org,
zokeefe@google.com
Subject: Re: [syzbot] KASAN: null-ptr-deref Read in hugepage_vma_check
Date: Sat, 25 Jun 2022 10:36:14 -0700 [thread overview]
Message-ID: <000000000000a4531805e2491f77@google.com> (raw)
In-Reply-To: <0000000000003189f305e19f5d3e@google.com>
syzbot has bisected this issue to:
commit 0a44ebaaa3f3ecfacd2744467957882eabd92cec
Author: Yang Shi <shy828301@gmail.com>
Date: Thu Jun 16 17:48:37 2022 +0000
mm: thp: kill transparent_hugepage_active()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=166ba760080000
start commit: 34d1d36073ea Add linux-next specific files for 20220621
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=156ba760080000
console output: https://syzkaller.appspot.com/x/log.txt?x=116ba760080000
kernel config: https://syzkaller.appspot.com/x/.config?x=b24b62d1c051cfc8
dashboard link: https://syzkaller.appspot.com/bug?extid=4d875b4d2e2b60bae9b4
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14097a3ff00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1466c63ff00000
Reported-by: syzbot+4d875b4d2e2b60bae9b4@syzkaller.appspotmail.com
Fixes: 0a44ebaaa3f3 ("mm: thp: kill transparent_hugepage_active()")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2022-06-25 17:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 7:04 [syzbot] KASAN: null-ptr-deref Read in hugepage_vma_check syzbot
2022-06-17 23:52 ` Andrew Morton
2022-06-18 0:14 ` Matthew Wilcox
2022-06-18 0:33 ` Yang Shi
2022-06-27 16:11 ` Zach O'Keefe
2022-06-27 18:13 ` Yang Shi
2022-06-21 15:10 ` syzbot
2022-06-25 17: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=000000000000a4531805e2491f77@google.com \
--to=syzbot+4d875b4d2e2b60bae9b4@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shy828301@gmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=willy@infradead.org \
--cc=zokeefe@google.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).