[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <82607566-fc73-5671-b230-4e9627e16aa3@redhat.com>
Date: Tue, 30 Aug 2016 17:03:03 +0200
From: Paolo Bonzini <pbonzini@...hat.com>
To: Dmitry Vyukov <dvyukov@...gle.com>
Cc: Robert Święcki <robert@...ecki.net>,
LKML <linux-kernel@...r.kernel.org>,
Borislav Petkov <bp@...en8.de>
Subject: Re: NULL-ptr deref in kvm_arch_vcpu_ioctl under AMD CPUs
On 30/08/2016 15:08, Dmitry Vyukov wrote:
>> > b21629da120 kvm: x86: avoid warning on repeated KVM_SET_TSS_ADDR
>> > 83676e92389 KVM: x86: avoid vmalloc(0) in the KVM_SET_CPUID
>> > 78e546c824f KVM: fail KVM_SET_VCPU_EVENTS with invalid exception number
>> > c622a3c21ed KVM: irqfd: fix NULL pointer dereference in kvm_irq_map_gsi
>> > f8c1b85b252 KVM: x86: avoid vmalloc(0) in the KVM_SET_CPUID
>> > d14bdb553f9 KVM: x86: fix OOPS after invalid KVM_SET_DEBUGREGS
>> > 250715a6171 KVM: x86: protect KVM_CREATE_PIT/KVM_CREATE_PIT2 with kvm->lock
>> > 4c5ea0a9cd0 locking/static_key: Fix concurrent static_key_slow_inc()
>> >
>> > The last one is responsible for most if not all of the OOPses with
>> > threads.
>
> I've started fuzzing kvm again. No crashes so far.
Fingers crossed! :)
Paolo
Powered by blists - more mailing lists