[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YuOPDpy+RqD09n3j@kroah.com>
Date: Fri, 29 Jul 2022 09:41:02 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Coleman Dietsch <dietschc@....edu>
Cc: kvm@...r.kernel.org, x86@...nel.org,
Sean Christopherson <seanjc@...gle.com>,
Dave Hansen <dave.hansen@...ux.intel.com>,
linux-kernel@...r.kernel.org,
syzbot+e54f930ed78eb0f85281@...kaller.appspotmail.com,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
"H . Peter Anvin" <hpa@...or.com>,
Paolo Bonzini <pbonzini@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
Pavel Skripkin <paskripkin@...il.com>,
linux-kernel-mentees@...ts.linuxfoundation.org
Subject: Re: [PATCH] KVM: x86/xen: Fix bug in kvm_xen_vcpu_set_attr()
On Thu, Jul 28, 2022 at 02:47:37PM -0500, Coleman Dietsch wrote:
> This crash appears to be happening when vcpu->arch.xen.timer is already set and kvm_xen_init_timer(vcpu) is called.
What does "this crash" refer to ?
>
> During testing with the syzbot reproducer code it seemed apparent that the else if statement in the KVM_XEN_VCPU_ATTR_TYPE_TIMER switch case was not being reached, which is where the kvm_xen_stop_timer(vcpu) call is located.
Please properly wrap your kernel changelog at 72 columns.
Didn't checkpatch.pl complain about this?
thanks,
greg k-h
Powered by blists - more mailing lists