public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [jgunthorpe:vfio_iommufd 25/29] drivers/vfio/vfio_main.c:600: undefined reference to `iommufd_vfio_compat_ioas_id'
Date: Sat, 20 Aug 2022 13:18:56 +0800	[thread overview]
Message-ID: <202208201310.oYoCaywG-lkp@intel.com> (raw)

tree:   https://github.com/jgunthorpe/linux vfio_iommufd
head:   d2ab4343c9f524e9404059830828188b0f8a15b6
commit: 41be72284fea27e79bd85a42d1967b13d7f26147 [25/29] vfio-iommufd: Allow iommufd to be used in place of a container fd
config: microblaze-randconfig-r001-20220820 (https://download.01.org/0day-ci/archive/20220820/202208201310.oYoCaywG-lkp@intel.com/config)
compiler: microblaze-linux-gcc (GCC) 12.1.0
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://github.com/jgunthorpe/linux/commit/41be72284fea27e79bd85a42d1967b13d7f26147
        git remote add jgunthorpe https://github.com/jgunthorpe/linux
        git fetch --no-tags jgunthorpe vfio_iommufd
        git checkout 41be72284fea27e79bd85a42d1967b13d7f26147
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=microblaze SHELL=/bin/bash

If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   microblaze-linux-ld: drivers/vfio/vfio_main.o: in function `vfio_group_ioctl_set_container':
>> drivers/vfio/vfio_main.c:600: undefined reference to `iommufd_vfio_compat_ioas_id'


vim +600 drivers/vfio/vfio_main.c

   568	
   569	static int vfio_group_ioctl_set_container(struct vfio_group *group,
   570						  int __user *arg)
   571	{
   572		struct vfio_container *container;
   573		struct iommufd_ctx *iommufd;
   574		struct fd f;
   575		int ret = -EINVAL;
   576		int fd;
   577	
   578		if (get_user(fd, arg))
   579			return -EFAULT;
   580	
   581		f = fdget(fd);
   582		if (!f.file)
   583			return -EBADF;
   584	
   585		down_write(&group->group_rwsem);
   586		if (vfio_group_has_container(group))
   587			goto out_unlock;
   588	
   589		container = vfio_container_from_file(f.file);
   590		if (container) {
   591			ret = vfio_container_attach_group(group, container);
   592			goto out_unlock;
   593		}
   594	
   595		iommufd = iommufd_ctx_from_file(f.file);
   596		if (!IS_ERR(iommufd)) {
   597			u32 ioas_id;
   598	
   599			group->iommufd = iommufd;
 > 600			ret = iommufd_vfio_compat_ioas_id(iommufd, &ioas_id);
   601			goto out_unlock;
   602		}
   603	
   604	out_unlock:
   605		up_write(&group->group_rwsem);
   606		fdput(f);
   607		return ret;
   608	}
   609	

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

                 reply	other threads:[~2022-08-20  5:19 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=202208201310.oYoCaywG-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=jgg@nvidia.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.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