From: Sean Christopherson <sean.j.christopherson@intel.com>
To: syzbot <syzbot+00be5da1d75f1cc95f6b@syzkaller.appspotmail.com>
Cc: bp@alien8.de, hpa@zytor.com, jmattson@google.com,
joro@8bytes.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, mingo@redhat.com,
pbonzini@redhat.com, rkrcmar@redhat.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
vkuznets@redhat.com, wanpengli@tencent.com, x86@kernel.org
Subject: Re: WARNING in vcpu_enter_guest
Date: Thu, 19 Mar 2020 07:49:52 -0700 [thread overview]
Message-ID: <20200319144952.GB11305@linux.intel.com> (raw)
In-Reply-To: <00000000000081861f05a132b9cd@google.com>
On Thu, Mar 19, 2020 at 03:35:16AM -0700, syzbot wrote:
> syzbot has found a reproducer for the following crash on:
>
> HEAD commit: 5076190d mm: slub: be more careful about the double cmpxch..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=143ca61de00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=9f894bd92023de02
> dashboard link: https://syzkaller.appspot.com/bug?extid=00be5da1d75f1cc95f6b
> compiler: gcc (GCC) 9.0.0 20181231 (experimental)
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10bb4023e00000
>
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by: syzbot+00be5da1d75f1cc95f6b@syzkaller.appspotmail.com
Reproduced with a little tweaking of the reproducer, debug in progress.
next prev parent reply other threads:[~2020-03-19 14:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 8:20 WARNING in vcpu_enter_guest syzbot
2020-03-19 10:35 ` syzbot
2020-03-19 14:49 ` Sean Christopherson [this message]
2020-03-19 15:14 ` Paolo Bonzini
2020-03-19 17:35 ` Sean Christopherson
2020-03-19 17:39 ` Sean Christopherson
2020-03-19 17:44 ` Paolo Bonzini
2020-03-20 0:18 ` Thomas Gleixner
2020-03-20 10:33 ` Paolo Bonzini
2020-03-20 13:33 ` Thomas Gleixner
2020-03-22 3:31 ` 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=20200319144952.GB11305@linux.intel.com \
--to=sean.j.christopherson@intel.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=syzbot+00be5da1d75f1cc95f6b@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--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