From: syzbot <syzbot+7423f066b632d9ff23d5@syzkaller.appspotmail.com>
To: 42.hyeyoo@gmail.com, akpm@linux-foundation.org, bhe@redhat.com,
dyoung@redhat.com, hughd@google.com, kexec@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
llvm@lists.linux.dev, lrh2000@pku.edu.cn,
mike.kravetz@oracle.com, muchun.song@linux.dev,
nathan@kernel.org, ndesaulniers@google.com, pcc@google.com,
syzkaller-bugs@googlegroups.com, trix@redhat.com,
vgoyal@redhat.com, willy@infradead.org
Subject: Re: [syzbot] [mm?] kernel BUG in free_unref_page_prepare
Date: Fri, 01 Sep 2023 07:16:34 -0700 [thread overview]
Message-ID: <000000000000d5052e06044cced1@google.com> (raw)
In-Reply-To: <0000000000001f4d4806037fc7b8@google.com>
syzbot has bisected this issue to:
commit 3a77b282e256d880791a4c5aa10ede13d6417425
Author: Matthew Wilcox (Oracle) <willy@infradead.org>
Date: Wed Aug 16 15:11:58 2023 +0000
mm: free up a word in the first tail page
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13297387a80000
start commit: 7271b2a53042 Add linux-next specific files for 20230818
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=10a97387a80000
console output: https://syzkaller.appspot.com/x/log.txt?x=17297387a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=1936af09cdef7dd6
dashboard link: https://syzkaller.appspot.com/bug?extid=7423f066b632d9ff23d5
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=112386f3a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15044717a80000
Reported-by: syzbot+7423f066b632d9ff23d5@syzkaller.appspotmail.com
Fixes: 3a77b282e256 ("mm: free up a word in the first tail page")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-09-01 14:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 9:39 [syzbot] [mm?] kernel BUG in free_unref_page_prepare syzbot
2023-08-22 17:25 ` Mike Kravetz
2023-09-01 14:16 ` 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=000000000000d5052e06044cced1@google.com \
--to=syzbot+7423f066b632d9ff23d5@syzkaller.appspotmail.com \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=dyoung@redhat.com \
--cc=hughd@google.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=llvm@lists.linux.dev \
--cc=lrh2000@pku.edu.cn \
--cc=mike.kravetz@oracle.com \
--cc=muchun.song@linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=pcc@google.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=trix@redhat.com \
--cc=vgoyal@redhat.com \
--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