From: kbuild test robot <lkp@intel.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: kbuild-all@01.org, linux-rt-users@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
kvm@vger.kernel.org
Subject: Re: [PATCH -rt] kvm: lockdep annotate mmu_lock wait_lock
Date: Wed, 19 Jul 2017 23:59:18 +0800 [thread overview]
Message-ID: <201707192304.NFa8BhpY%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170718120347.GA25342@amt.cnet>
[-- Attachment #1: Type: text/plain, Size: 2469 bytes --]
Hi Marcelo,
[auto build test ERROR on linux-rt-devel/for-kbuild-bot/current-stable]
url: https://github.com/0day-ci/linux/commits/Marcelo-Tosatti/kvm-lockdep-annotate-mmu_lock-wait_lock/20170719-025327
base: https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git for-kbuild-bot/current-stable
config: x86_64-allyesdebian (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
In file included from include/linux/hardirq.h:5:0,
from include/linux/kvm_host.h:10,
from arch/x86/kvm/../../../virt/kvm/kvm_main.c:21:
arch/x86/kvm/../../../virt/kvm/kvm_main.c: In function 'kvm_create_vm':
>> arch/x86/kvm/../../../virt/kvm/kvm_main.c:617:45: error: 'spinlock_t {aka struct spinlock}' has no member named 'lock'; did you mean 'rlock'?
lockdep_set_novalidate_class(&kvm->mmu_lock.lock.wait_lock);
^
include/linux/lockdep.h:300:22: note: in definition of macro 'lockdep_set_class_and_name'
lockdep_init_map(&(lock)->dep_map, name, key, 0)
^~~~
arch/x86/kvm/../../../virt/kvm/kvm_main.c:617:2: note: in expansion of macro 'lockdep_set_novalidate_class'
lockdep_set_novalidate_class(&kvm->mmu_lock.lock.wait_lock);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +617 arch/x86/kvm/../../../virt/kvm/kvm_main.c
606
607 static struct kvm *kvm_create_vm(unsigned long type)
608 {
609 int r, i;
610 struct kvm *kvm = kvm_arch_alloc_vm();
611
612 if (!kvm)
613 return ERR_PTR(-ENOMEM);
614
615 spin_lock_init(&kvm->mmu_lock);
616
> 617 lockdep_set_novalidate_class(&kvm->mmu_lock.lock.wait_lock);
618 mmgrab(current->mm);
619 kvm->mm = current->mm;
620 kvm_eventfd_init(kvm);
621 mutex_init(&kvm->lock);
622 mutex_init(&kvm->irq_lock);
623 mutex_init(&kvm->slots_lock);
624 refcount_set(&kvm->users_count, 1);
625 INIT_LIST_HEAD(&kvm->devices);
626
627 r = kvm_arch_init_vm(kvm, type);
628 if (r)
629 goto out_err_no_disable;
630
631 r = hardware_enable_all();
632 if (r)
633 goto out_err_no_disable;
634
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 38522 bytes --]
next prev parent reply other threads:[~2017-07-19 15:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 12:03 [PATCH -rt] kvm: lockdep annotate mmu_lock wait_lock Marcelo Tosatti
2017-07-18 12:16 ` Peter Zijlstra
2017-07-18 12:22 ` Marcelo Tosatti
2017-07-18 12:45 ` Peter Zijlstra
2017-07-19 20:31 ` Julia Cartwright
2017-07-19 15:59 ` kbuild test robot [this message]
2017-07-20 2:35 ` kbuild test robot
2017-08-07 13:35 ` Sebastian Andrzej Siewior
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=201707192304.NFa8BhpY%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=kvm@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=peterz@infradead.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