All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android16-6.12 3/3] arch/arm64/kvm/../../../virt/kvm/vfio.c:130:undefined reference to `vfio_file_iommu_group'
Date: Tue, 01 Sep 2026 07:41:46 +0800	[thread overview]
Message-ID: <202609010710.aoWhYncr-lkp@intel.com> (raw)

tree:   https://android.googlesource.com/kernel/common android16-6.12
head:   96b3287eace89e145c28c3461ed3d8c8ea0b2baa
commit: e43f03eb172d7e8ecac55bc3f9547c18f436ea82 [3/3] ANDROID: drivers/vfio: Call KVM directly
config: arm64-randconfig-004-20260829 (https://download.01.org/0day-ci/archive/20260901/202609010710.aoWhYncr-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 15.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260901/202609010710.aoWhYncr-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/202609010710.aoWhYncr-lkp@intel.com/

All errors (new ones prefixed by >>):

   aarch64-linux-ld: Unexpected GOT/PLT entries detected!
   aarch64-linux-ld: Unexpected run-time procedure linkages detected!
   aarch64-linux-ld: virt/kvm/vfio.o: in function `kvm_vfio_reclaim_file':
>> arch/arm64/kvm/../../../virt/kvm/vfio.c:130:(.text+0x21c): undefined reference to `vfio_file_iommu_group'
   aarch64-linux-ld: virt/kvm/vfio.o: in function `kvm_vfio_file_add':
   arch/arm64/kvm/../../../virt/kvm/vfio.c:130:(.text+0xc74): undefined reference to `vfio_file_iommu_group'


vim +130 arch/arm64/kvm/../../../virt/kvm/vfio.c

   125	
   126	static struct iommu_group *kvm_vfio_file_iommu_group(struct file *file)
   127	{
   128		/* See kvm_vfio_file_set_kvm() */
   129	#if IS_BUILTIN(CONFIG_VFIO)
 > 130		return vfio_file_iommu_group(file);
   131	#else
   132		struct iommu_group *(*fn)(struct file *file);
   133		struct iommu_group *ret;
   134	
   135		fn = symbol_get(vfio_file_iommu_group);
   136		if (!fn)
   137			return NULL;
   138	
   139		ret = fn(file);
   140	
   141		symbol_put(vfio_file_iommu_group);
   142	
   143		return ret;
   144	#endif
   145	}
   146	

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

                 reply	other threads:[~2026-08-31 23:42 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=202609010710.aoWhYncr-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=cros-kernel-buildreports@googlegroups.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.