From: Paolo Bonzini <pbonzini@redhat.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: syzbot <syzbot+01bc9e7a8a3f138b71cf@syzkaller.appspotmail.com>,
"H. Peter Anvin" <hpa@zytor.com>,
"KVM list" <kvm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"Ingo Molnar" <mingo@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"the arch/x86 maintainers" <x86@kernel.org>
Subject: Re: WARNING in free_loaded_vmcs (2)
Date: Tue, 21 Aug 2018 18:42:44 +0200 [thread overview]
Message-ID: <f7eb5c68-97af-86a3-b253-4bee36e7d1de@redhat.com> (raw)
In-Reply-To: <CACT4Y+aA8SzNeYu3YmWLoKbx6J-O_drbV_okX4WoOWzyoxem6Q@mail.gmail.com>
On 14/08/2018 22:41, Dmitry Vyukov wrote:
> On Tue, Aug 14, 2018 at 10:16 AM, Paolo Bonzini <pbonzini@redhat.com> wrote:
>> Is there anything that was changed in syzkaller and is causing it to
>> find all these bugs?
> Nothing has changed on syzkaller side as far as I can tell.
And the failures started to appear on 20180806 when I did the big KVM
update from 85eae57bbb0612387201635659be543aaac2109e to
8c154ff6ee99d2d467c3c964ef6a478ca7614155.
They all seem related to some use-after-free on exit, and there is a
reproducer at https://syzkaller.appspot.com/x/repro.c?x=122d6672400000,
but it doesn't immediately cause the failure for me.
Paolo
next prev parent reply other threads:[~2018-08-21 16:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-14 12:46 syzbot
2018-08-14 17:16 ` Paolo Bonzini
2018-08-14 20:41 ` Dmitry Vyukov
2018-08-21 16:42 ` Paolo Bonzini [this message]
2018-09-04 2:41 ` syzbot
2019-03-31 4:53 ` syzbot
2019-04-01 19:16 ` Sean Christopherson
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=f7eb5c68-97af-86a3-b253-4bee36e7d1de@redhat.com \
--to=pbonzini@redhat.com \
--cc=dvyukov@google.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=syzbot+01bc9e7a8a3f138b71cf@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--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
all inboxes | Powered by JetHome®