From: kernel test robot <lkp@intel.com>
To: Joao Martins <joao.m.martins@oracle.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Jason Gunthorpe <jgg@ziepe.ca>, Kevin Tian <kevin.tian@intel.com>
Subject: [linux-next:master 11306/14422] drivers/iommu/iommufd/hw_pagetable.c:234:undefined reference to `__udivdi3'
Date: Tue, 24 Oct 2023 02:35:12 +0800 [thread overview]
Message-ID: <202310240246.FyXNZrbZ-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: e8361b005d7c92997d12f2b85a9e4a525738bd9d
commit: 1337d793ea254e9b6e79568e1dd063c6ed8c2741 [11306/14422] iommufd: Add IOMMU_HWPT_GET_DIRTY_BITMAP
config: microblaze-randconfig-r015-20230422 (https://download.01.org/0day-ci/archive/20231024/202310240246.FyXNZrbZ-lkp@intel.com/config)
compiler: microblaze-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231024/202310240246.FyXNZrbZ-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/202310240246.FyXNZrbZ-lkp@intel.com/
All errors (new ones prefixed by >>):
microblaze-linux-ld: drivers/iommu/iommufd/hw_pagetable.o: in function `iommufd_check_iova_range':
>> drivers/iommu/iommufd/hw_pagetable.c:234:(.text+0x99c): undefined reference to `__udivdi3'
microblaze-linux-ld: drivers/iommu/iommufd/hw_pagetable.o: in function `iommufd_hwpt_get_dirty_bitmap':
drivers/iommu/iommufd/hw_pagetable.c:234:(.text+0xa6c): undefined reference to `__udivdi3'
vim +234 drivers/iommu/iommufd/hw_pagetable.c
223
224 int iommufd_check_iova_range(struct iommufd_ioas *ioas,
225 struct iommu_hwpt_get_dirty_bitmap *bitmap)
226 {
227 unsigned long npages;
228 size_t iommu_pgsize;
229 int rc = -EINVAL;
230
231 if (!bitmap->page_size)
232 return rc;
233
> 234 npages = bitmap->length / bitmap->page_size;
235 if (!npages || (npages > ULONG_MAX))
236 return rc;
237
238 iommu_pgsize = ioas->iopt.iova_alignment;
239
240 if (bitmap->iova & (iommu_pgsize - 1))
241 return rc;
242
243 if (!bitmap->length || bitmap->length & (iommu_pgsize - 1))
244 return rc;
245
246 return 0;
247 }
248
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-10-23 18:36 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=202310240246.FyXNZrbZ-lkp@intel.com \
--to=lkp@intel.com \
--cc=jgg@ziepe.ca \
--cc=joao.m.martins@oracle.com \
--cc=kevin.tian@intel.com \
--cc=linux-mm@kvack.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox