From: syzbot <syzbot+75475908cd0910f141ee@syzkaller.appspotmail.com>
To: jmattson@google.com, jsperbeck@google.com, junaids@google.com,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
pbonzini@redhat.com, rkrcmar@redhat.com,
syzkaller-bugs@googlegroups.com
Subject: Re: WARNING: suspicious RCU usage in kvm_dev_ioctl
Date: Sat, 02 Nov 2019 21:36:01 -0700 [thread overview]
Message-ID: <000000000000742ddc059669bc92@google.com> (raw)
In-Reply-To: <000000000000bd85b40596657dfa@google.com>
syzbot has bisected this bug to:
commit a97b0e773e492ae319a7e981e98962a1060215f9
Author: Jim Mattson <jmattson@google.com>
Date: Fri Oct 25 11:34:58 2019 +0000
kvm: call kvm_arch_destroy_vm if vm creation fails
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13f19914e00000
start commit: 9d234505 Merge tag 'hwmon-for-v5.4-rc6' of git://git.kerne..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=10099914e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=17f19914e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=cbbed3e8d4eb64bf
dashboard link: https://syzkaller.appspot.com/bug?extid=75475908cd0910f141ee
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14e20268e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15209b84e00000
Reported-by: syzbot+75475908cd0910f141ee@syzkaller.appspotmail.com
Fixes: a97b0e773e49 ("kvm: call kvm_arch_destroy_vm if vm creation fails")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2019-11-03 4:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-02 23:32 WARNING: suspicious RCU usage in kvm_dev_ioctl syzbot
2019-11-03 0:27 ` syzbot
2019-11-03 4: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=000000000000742ddc059669bc92@google.com \
--to=syzbot+75475908cd0910f141ee@syzkaller.appspotmail.com \
--cc=jmattson@google.com \
--cc=jsperbeck@google.com \
--cc=junaids@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox