Am 22.01.2017 um 10:04 schrieb Dmitry Vyukov: > Currently svm_vm_data_hash_lock is left uninitialized. > This causes lockdep warnings. Properly initialize it. > > Signed-off-by: Dmitry Vyukov <dvyukov@xxxxxxxxxx> > Cc: Joerg Roedel <joro@xxxxxxxxxx> > Cc: Paolo Bonzini <pbonzini@xxxxxxxxxx> > Cc: "Radim Krčmář" <rkrcmar@xxxxxxxxxx> > Cc: kvm@xxxxxxxxxxxxxxx > Cc: syzkaller@xxxxxxxxxxxxxxxx > --- > arch/x86/kvm/svm.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/arch/x86/kvm/svm.c b/arch/x86/kvm/svm.c > index 08a4d3ab3455..b928a9c34987 100644 > --- a/arch/x86/kvm/svm.c > +++ b/arch/x86/kvm/svm.c > @@ -972,7 +972,7 @@ static void svm_disable_lbrv(struct vcpu_svm *svm) > */ > #define SVM_VM_DATA_HASH_BITS 8 > DECLARE_HASHTABLE(svm_vm_data_hash, SVM_VM_DATA_HASH_BITS); > -static spinlock_t svm_vm_data_hash_lock; > +static DEFINE_SPINLOCK(svm_vm_data_hash_lock); > > /* Note: > * This function is called from IOMMU driver to notify > We have spin_lock_init(&svm_vm_data_hash_lock); in svm_hardware_setup(). If this isn't called, wouldn't the right fix be to find out why? -- David
