[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f7eb5c68-97af-86a3-b253-4bee36e7d1de@redhat.com>
Date: Tue, 21 Aug 2018 18:42:44 +0200
From: Paolo Bonzini <pbonzini@...hat.com>
To: Dmitry Vyukov <dvyukov@...gle.com>
Cc: syzbot <syzbot+01bc9e7a8a3f138b71cf@...kaller.appspotmail.com>,
"H. Peter Anvin" <hpa@...or.com>, KVM list <kvm@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...hat.com>,
Radim Krčmář <rkrcmar@...hat.com>,
syzkaller-bugs <syzkaller-bugs@...glegroups.com>,
Thomas Gleixner <tglx@...utronix.de>,
the arch/x86 maintainers <x86@...nel.org>
Subject: Re: WARNING in free_loaded_vmcs (2)
On 14/08/2018 22:41, Dmitry Vyukov wrote:
> On Tue, Aug 14, 2018 at 10:16 AM, Paolo Bonzini <pbonzini@...hat.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
Powered by blists - more mailing lists