Linux s390 Architecture development
 help / color / mirror / Atom feed
* [kvms390:sae 2/54] arch/x86/kvm/svm/sev.c:117:32: error: 'struct kvm' has no member named 'users_count'
@ 2026-05-12 12:47 kernel test robot
  0 siblings, 0 replies; only message in thread
From: kernel test robot @ 2026-05-12 12:47 UTC (permalink / raw)
  To: Paolo Bonzini; +Cc: oe-kbuild-all, linux-s390, Steffen Eiden

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-rhel-9.4-bpf (https://download.01.org/0day-ci/archive/20260512/202605122020.wEdQHOry-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260512/202605122020.wEdQHOry-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/202605122020.wEdQHOry-lkp@intel.com/

All errors (new ones prefixed by >>):

   arch/x86/kvm/svm/sev.c: In function 'kvm_lockdep_assert_sev_lock_held':
>> arch/x86/kvm/svm/sev.c:117:32: error: 'struct kvm' has no member named 'users_count'
     117 |         if (!refcount_read(&kvm->users_count))
         |                                ^~


vim +117 arch/x86/kvm/svm/sev.c

eaf78265a4ab33 Joerg Roedel        2020-03-24  109  
ba903f73824907 Sean Christopherson 2026-03-10  110  static __always_inline void kvm_lockdep_assert_sev_lock_held(struct kvm *kvm)
ba903f73824907 Sean Christopherson 2026-03-10  111  {
ba903f73824907 Sean Christopherson 2026-03-10  112  #ifdef CONFIG_PROVE_LOCKING
ba903f73824907 Sean Christopherson 2026-03-10  113  	/*
ba903f73824907 Sean Christopherson 2026-03-10  114  	 * Querying SEV+ support is safe if there are no other references, i.e.
ba903f73824907 Sean Christopherson 2026-03-10  115  	 * if concurrent initialization of SEV+ is impossible.
ba903f73824907 Sean Christopherson 2026-03-10  116  	 */
ba903f73824907 Sean Christopherson 2026-03-10 @117  	if (!refcount_read(&kvm->users_count))
ba903f73824907 Sean Christopherson 2026-03-10  118  		return;
ba903f73824907 Sean Christopherson 2026-03-10  119  
ba903f73824907 Sean Christopherson 2026-03-10  120  	/*
ba903f73824907 Sean Christopherson 2026-03-10  121  	 * Querying SEV+ support from vCPU context is always safe, as vCPUs can
ba903f73824907 Sean Christopherson 2026-03-10  122  	 * only be created after SEV+ is initialized (and KVM disallows all SEV
ba903f73824907 Sean Christopherson 2026-03-10  123  	 * sub-ioctls while vCPU creation is in-progress).
ba903f73824907 Sean Christopherson 2026-03-10  124  	 */
ba903f73824907 Sean Christopherson 2026-03-10  125  	if (kvm_get_running_vcpu())
ba903f73824907 Sean Christopherson 2026-03-10  126  		return;
ba903f73824907 Sean Christopherson 2026-03-10  127  
ba903f73824907 Sean Christopherson 2026-03-10  128  	lockdep_assert_held(&kvm->lock);
ba903f73824907 Sean Christopherson 2026-03-10  129  #endif
ba903f73824907 Sean Christopherson 2026-03-10  130  }
ba903f73824907 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

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2026-05-12 12:47 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-05-12 12:47 [kvms390:sae 2/54] arch/x86/kvm/svm/sev.c:117:32: error: 'struct kvm' has no member named 'users_count' kernel test robot

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox