On Wed, 25 Jun 2025 00:23:03 +0800, kernel test robot <lkp@xxxxxxxxx> wrote: > kernel test robot noticed the following build errors: > > [auto build test ERROR on awilliam-vfio/next] > [also build test ERROR on awilliam-vfio/for-linus linus/master v6.16-rc3 next-20250624] > [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/lizhe-67-bytedance-com/vfio-type1-batch-vfio_find_vpfn-in-function-vfio_unpin_pages_remote/20250620-112605 > base: https://github.com/awilliam/linux-vfio.git next > patch link: https://lore.kernel.org/r/20250620032344.13382-2-lizhe.67%40bytedance.com > patch subject: [PATCH v5 1/3] vfio/type1: batch vfio_find_vpfn() in function vfio_unpin_pages_remote() > config: x86_64-rhel-9.4 (https://download.01.org/0day-ci/archive/20250625/202506250037.VfdBAPP3-lkp@xxxxxxxxx/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/20250625/202506250037.VfdBAPP3-lkp@xxxxxxxxx/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@xxxxxxxxx> > | Closes: https://lore.kernel.org/oe-kbuild-all/202506250037.VfdBAPP3-lkp@xxxxxxxxx/ > > All errors (new ones prefixed by >>): > > drivers/vfio/vfio_iommu_type1.c: In function 'vfio_unpin_pages_remote': > >> drivers/vfio/vfio_iommu_type1.c:738:37: error: implicit declaration of function 'vpfn_pages'; did you mean 'vma_pages'? [-Werror=implicit-function-declaration] > 738 | long unlocked = 0, locked = vpfn_pages(dma, iova, npage); > | ^~~~~~~~~~ > | vma_pages > cc1: some warnings being treated as errors Perhaps we need to compile with this patch[1] included to avoid build errors. Thanks, Zhe [1]: https://lore.kernel.org/all/20250529064947.38433-1-lizhe.67@xxxxxxxxxxxxx/