From: syzbot <syzbot+5ea2845f44caa77f5543@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, axboe@kernel.dk,
borntraeger@linux.ibm.com, david@redhat.com,
frankja@linux.ibm.com, imbrenda@linux.ibm.com,
io-uring@vger.kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-mm@kvack.org, pbonzini@redhat.com, peterx@redhat.com,
shuah@kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] WARNING in hpage_collapse_scan_pmd (2)
Date: Thu, 01 Aug 2024 10:57:02 -0700 [thread overview]
Message-ID: <0000000000001fdcda061ea2f073@google.com> (raw)
In-Reply-To: <0000000000006923bb06178ce04a@google.com>
syzbot has bisected this issue to:
commit ef5b6a542b1dbb718226a5f8208be09ef405983d
Author: Paolo Bonzini <pbonzini@redhat.com>
Date: Wed Nov 8 09:40:35 2023 +0000
selftests: kvm/s390x: use vm_create_barebones()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14071cd3980000
start commit: e67572cd2204 Linux 6.9-rc6
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=16071cd3980000
console output: https://syzkaller.appspot.com/x/log.txt?x=12071cd3980000
kernel config: https://syzkaller.appspot.com/x/.config?x=3310e643b6ef5d69
dashboard link: https://syzkaller.appspot.com/bug?extid=5ea2845f44caa77f5543
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10874a40980000
Reported-by: syzbot+5ea2845f44caa77f5543@syzkaller.appspotmail.com
Fixes: ef5b6a542b1d ("selftests: kvm/s390x: use vm_create_barebones()")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-08-01 17:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 13:41 [syzbot] [mm?] [io-uring?] WARNING in hpage_collapse_scan_pmd (2) syzbot
2024-05-06 9:04 ` David Hildenbrand
2024-05-06 16:14 ` syzbot
2024-08-01 17:57 ` syzbot [this message]
2024-08-15 16:10 ` [syzbot] [mm?] " syzbot
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=0000000000001fdcda061ea2f073@google.com \
--to=syzbot+5ea2845f44caa77f5543@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=borntraeger@linux.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=io-uring@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=shuah@kernel.org \
--cc=syzkaller-bugs@googlegroups.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 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.