public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Maxim Levitsky <mlevitsk@redhat.com>, kvm@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, "H. Peter Anvin" <hpa@zytor.com>,
	x86@kernel.org, Maxim Levitsky <mlevitsk@redhat.com>,
	Randy Dunlap <rdunlap@infradead.org>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Will Deacon <will@kernel.org>,
	Oliver Upton <oliver.upton@linux.dev>,
	Kunkun Jiang <jiangkunkun@huawei.com>,
	Jing Zhang <jingzhangos@google.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Keisuke Nishimura <keisuke.nishimura@inria.fr>,
	Anup Patel <anup@brainfault.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Atish Patra <atishp@atishpatra.org>,
	kvmarm@lists.linux.dev, Waiman Long <longman@redhat.com>,
	Boqun Feng <boqun.feng@gmail.com>,
	linux-arm-kernel@lists.infradead.org,
	Peter Zijlstra <peterz@infradead.org>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Zenghui Yu <yuzenghui@huawei.com>,
	Sebastian Ott <sebott@redhat.com>,
	Andre Przywara <andre.przywara@arm.com>,
	Ingo Molnar <mingo@redhat.com>, Alexandre Ghiti <alex@ghiti.fr>,
	Bjorn Helgaas <helgaas@kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>
Subject: Re: [PATCH v3 1/4] arm64: KVM: use mutex_trylock_nest_lock when locking all vCPUs
Date: Thu, 8 May 2025 01:04:31 +0800	[thread overview]
Message-ID: <202505080024.CZZ0ssB5-lkp@intel.com> (raw)
In-Reply-To: <20250430202311.364641-2-mlevitsk@redhat.com>

Hi Maxim,

kernel test robot noticed the following build errors:

[auto build test ERROR on kvm/queue]
[also build test ERROR on kvm/next kvmarm/next tip/locking/core linus/master v6.15-rc5 next-20250507]
[cannot apply to kvm/linux-next]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Maxim-Levitsky/arm64-KVM-use-mutex_trylock_nest_lock-when-locking-all-vCPUs/20250501-042643
base:   https://git.kernel.org/pub/scm/virt/kvm/kvm.git queue
patch link:    https://lore.kernel.org/r/20250430202311.364641-2-mlevitsk%40redhat.com
patch subject: [PATCH v3 1/4] arm64: KVM: use mutex_trylock_nest_lock when locking all vCPUs
config: x86_64-rhel-9.4 (https://download.01.org/0day-ci/archive/20250508/202505080024.CZZ0ssB5-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250508/202505080024.CZZ0ssB5-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/202505080024.CZZ0ssB5-lkp@intel.com/

All errors (new ones prefixed by >>):

   arch/x86/kvm/../../../virt/kvm/kvm_main.c: In function 'kvm_trylock_all_vcpus':
>> arch/x86/kvm/../../../virt/kvm/kvm_main.c:1381:22: error: implicit declaration of function 'mutex_trylock_nest_lock'; did you mean 'mutex_lock_nest_lock'? [-Werror=implicit-function-declaration]
    1381 |                 if (!mutex_trylock_nest_lock(&vcpu->mutex, &kvm->lock))
         |                      ^~~~~~~~~~~~~~~~~~~~~~~
         |                      mutex_lock_nest_lock
   cc1: some warnings being treated as errors


vim +1381 arch/x86/kvm/../../../virt/kvm/kvm_main.c

  1370	
  1371	/*
  1372	 * Try to lock all of the VM's vCPUs.
  1373	 * Assumes that the kvm->lock is held.
  1374	 */
  1375	int kvm_trylock_all_vcpus(struct kvm *kvm)
  1376	{
  1377		struct kvm_vcpu *vcpu;
  1378		unsigned long i, j;
  1379	
  1380		kvm_for_each_vcpu(i, vcpu, kvm)
> 1381			if (!mutex_trylock_nest_lock(&vcpu->mutex, &kvm->lock))
  1382				goto out_unlock;
  1383		return 0;
  1384	
  1385	out_unlock:
  1386		kvm_for_each_vcpu(j, vcpu, kvm) {
  1387			if (i == j)
  1388				break;
  1389			mutex_unlock(&vcpu->mutex);
  1390		}
  1391		return -EINTR;
  1392	}
  1393	EXPORT_SYMBOL_GPL(kvm_trylock_all_vcpus);
  1394	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


  reply	other threads:[~2025-05-07 17:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-30 20:23 [PATCH v3 0/4] KVM: lockdep improvements Maxim Levitsky
2025-04-30 20:23 ` [PATCH v3 1/4] arm64: KVM: use mutex_trylock_nest_lock when locking all vCPUs Maxim Levitsky
2025-05-07 17:04   ` kernel test robot [this message]
2025-04-30 20:23 ` [PATCH v3 2/4] RISC-V: KVM: switch to kvm_lock/unlock_all_vcpus Maxim Levitsky
2025-04-30 20:23 ` [PATCH v3 3/4] locking/mutex: implement mutex_lock_killable_nest_lock Maxim Levitsky
2025-04-30 20:23 ` [PATCH v3 4/4] x86: KVM: SEV: implement kvm_lock_all_vcpus and use it Maxim Levitsky
2025-04-30 20:30 ` [PATCH v3 0/4] KVM: lockdep improvements mlevitsk

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=202505080024.CZZ0ssB5-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=alex@ghiti.fr \
    --cc=andre.przywara@arm.com \
    --cc=anup@brainfault.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=atishp@atishpatra.org \
    --cc=boqun.feng@gmail.com \
    --cc=catalin.marinas@arm.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=helgaas@kernel.org \
    --cc=hpa@zytor.com \
    --cc=jiangkunkun@huawei.com \
    --cc=jingzhangos@google.com \
    --cc=keisuke.nishimura@inria.fr \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.linux.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=longman@redhat.com \
    --cc=mingo@redhat.com \
    --cc=mlevitsk@redhat.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=oliver.upton@linux.dev \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=pbonzini@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rdunlap@infradead.org \
    --cc=sebott@redhat.com \
    --cc=suzuki.poulose@arm.com \
    --cc=will@kernel.org \
    --cc=x86@kernel.org \
    --cc=yuzenghui@huawei.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