From: syzbot <syzbot+760a73552f47a8cd0fd9@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, bp@alien8.de, gleb@kernel.org,
hpa@zytor.com, kernellwp@gmail.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, mingo@kernel.org, mingo@redhat.com,
paulmck@linux.vnet.ibm.com, pbonzini@redhat.com,
peterz@infradead.org, rkrcmar@redhat.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
torvalds@linux-foundation.org, x86@kernel.org
Subject: Re: WARNING in kvm_arch_vcpu_ioctl_run (3)
Date: Sun, 14 Apr 2019 04:06:00 -0700 [thread overview]
Message-ID: <00000000000064948e05867b8503@google.com> (raw)
In-Reply-To: <000000000000d05a78056873bc47@google.com>
syzbot has bisected this bug to:
commit 706249c222f68471b6f8e9e8e9b77665c404b226
Author: Peter Zijlstra <peterz@infradead.org>
Date: Fri Jul 24 13:06:37 2015 +0000
locking/static_keys: Rework update logic
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=175cc587200000
start commit: 1d2ba7fe Merge tag 'fbdev-v4.19-rc7' of https://github.com..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=14dcc587200000
console output: https://syzkaller.appspot.com/x/log.txt?x=10dcc587200000
kernel config: https://syzkaller.appspot.com/x/.config?x=c0af03fe452b65fb
dashboard link: https://syzkaller.appspot.com/bug?extid=760a73552f47a8cd0fd9
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=156ad231400000
Reported-by: syzbot+760a73552f47a8cd0fd9@syzkaller.appspotmail.com
Fixes: 706249c222f6 ("locking/static_keys: Rework update logic")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2019-04-14 11:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 7:13 WARNING in kvm_arch_vcpu_ioctl_run (3) syzbot
2018-03-28 7:29 ` Wanpeng Li
2022-06-22 2:46 ` Tetsuo Handa
2022-06-27 20:08 ` Sean Christopherson
2018-10-02 21:07 ` syzbot
2019-04-14 11:06 ` syzbot [this message]
2019-06-17 2:55 ` 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=00000000000064948e05867b8503@google.com \
--to=syzbot+760a73552f47a8cd0fd9@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=gleb@kernel.org \
--cc=hpa@zytor.com \
--cc=kernellwp@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=rkrcmar@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).