From: kernel test robot <lkp@intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-s390@vger.kernel.org, Steffen Eiden <seiden@linux.ibm.com>
Subject: [kvms390:sae 2/54] arch/x86/kvm/svm/sev.c:117:27: error: no member named 'users_count' in 'struct kvm'
Date: Wed, 13 May 2026 01:45:03 +0800 [thread overview]
Message-ID: <202605130154.8hoiUlcD-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git sae
head: e952fb65773b1e5cd2e5ca409e712db5ef252bb1
commit: 134336e0cba8dd18185738333bc26c1b0b020b6d [2/54] KVM, vfio: remove symbol_get(kvm_get_kvm_safe) from vfio
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20260513/202605130154.8hoiUlcD-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260513/202605130154.8hoiUlcD-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202605130154.8hoiUlcD-lkp@intel.com/
All errors (new ones prefixed by >>):
>> arch/x86/kvm/svm/sev.c:117:27: error: no member named 'users_count' in 'struct kvm'
117 | if (!refcount_read(&kvm->users_count))
| ~~~ ^
1 error generated.
vim +117 arch/x86/kvm/svm/sev.c
eaf78265a4ab339 Joerg Roedel 2020-03-24 109
ba903f738249077 Sean Christopherson 2026-03-10 110 static __always_inline void kvm_lockdep_assert_sev_lock_held(struct kvm *kvm)
ba903f738249077 Sean Christopherson 2026-03-10 111 {
ba903f738249077 Sean Christopherson 2026-03-10 112 #ifdef CONFIG_PROVE_LOCKING
ba903f738249077 Sean Christopherson 2026-03-10 113 /*
ba903f738249077 Sean Christopherson 2026-03-10 114 * Querying SEV+ support is safe if there are no other references, i.e.
ba903f738249077 Sean Christopherson 2026-03-10 115 * if concurrent initialization of SEV+ is impossible.
ba903f738249077 Sean Christopherson 2026-03-10 116 */
ba903f738249077 Sean Christopherson 2026-03-10 @117 if (!refcount_read(&kvm->users_count))
ba903f738249077 Sean Christopherson 2026-03-10 118 return;
ba903f738249077 Sean Christopherson 2026-03-10 119
ba903f738249077 Sean Christopherson 2026-03-10 120 /*
ba903f738249077 Sean Christopherson 2026-03-10 121 * Querying SEV+ support from vCPU context is always safe, as vCPUs can
ba903f738249077 Sean Christopherson 2026-03-10 122 * only be created after SEV+ is initialized (and KVM disallows all SEV
ba903f738249077 Sean Christopherson 2026-03-10 123 * sub-ioctls while vCPU creation is in-progress).
ba903f738249077 Sean Christopherson 2026-03-10 124 */
ba903f738249077 Sean Christopherson 2026-03-10 125 if (kvm_get_running_vcpu())
ba903f738249077 Sean Christopherson 2026-03-10 126 return;
ba903f738249077 Sean Christopherson 2026-03-10 127
ba903f738249077 Sean Christopherson 2026-03-10 128 lockdep_assert_held(&kvm->lock);
ba903f738249077 Sean Christopherson 2026-03-10 129 #endif
ba903f738249077 Sean Christopherson 2026-03-10 130 }
ba903f738249077 Sean Christopherson 2026-03-10 131
:::::: The code at line 117 was first introduced by commit
:::::: ba903f7382490776d2df2fca6bf5c8ef2eb4663f KVM: SEV: Assert that kvm->lock is held when querying SEV+ support
:::::: TO: Sean Christopherson <seanjc@google.com>
:::::: CC: Sean Christopherson <seanjc@google.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-05-12 17:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202605130154.8hoiUlcD-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-s390@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pbonzini@redhat.com \
--cc=seiden@linux.ibm.com \
/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