From: kernel test robot <lkp@intel.com>
To: Hajime Tazaki <thehajime@gmail.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Johannes Berg <johannes.berg@intel.com>,
Ricardo Koller <ricarkol@google.com>
Subject: [linux-next:master 9572/10910] drivers/pci/pci.c:4137:2: error: call to undeclared function 'vunmap_range'; ISO C99 and later do not support implicit function declarations
Date: Sun, 27 Sep 2026 06:11:35 +0200 [thread overview]
Message-ID: <202609270632.WSdFLSK0-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: f5f84daefcd92d7a630066635ecea1433ed5eac7
commit: 626ff2b34dbb7679b798f7a4962a8b3def695045 [9572/10910] um: allow deselecting CONFIG_MMU
config: um-randconfig-2001-20260927 (https://download.01.org/0day-ci/archive/20260927/202609270632.WSdFLSK0-lkp@intel.com/config)
compiler: clang version 22.1.8 (https://github.com/llvm/llvm-project ca7933e47d3a3451d81e72ac174dcb5aa28b59d1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260927/202609270632.WSdFLSK0-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/202609270632.WSdFLSK0-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from drivers/pci/pci.c:16:
In file included from include/linux/iommu.h:10:
In file included from include/linux/scatterlist.h:9:
In file included from arch/um/include/asm/io.h:24:
include/asm-generic/io.h:1209:55: warning: performing pointer arithmetic on a null pointer has undefined behavior [-Wnull-pointer-arithmetic]
1209 | return (port > MMIO_UPPER_LIMIT) ? NULL : PCI_IOBASE + port;
| ~~~~~~~~~~ ^
>> drivers/pci/pci.c:4137:2: error: call to undeclared function 'vunmap_range'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
4137 | vunmap_range(vaddr, vaddr + resource_size(res));
| ^
1 warning and 1 error generated.
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for PCI
Depends on [n]: HAVE_PCI [=y] && MMU [=n]
Selected by [y]:
- FORCE_PCI [=y]
WARNING: unmet direct dependencies detected for PM_GENERIC_DOMAINS_OF
Depends on [n]: PM_GENERIC_DOMAINS [=y] && OF [=n]
Selected by [y]:
- COMMON_CLK_MT8173_MFGTOP [=y] && COMMON_CLK [=y] && (ARCH_MEDIATEK || COMPILE_TEST [=y]) && COMMON_CLK_MT8173 [=y] && PM [=y]
vim +/vunmap_range +4137 drivers/pci/pci.c
8b921acfeffdb0 Liviu Dudau 2014-09-29 4123
4d3f13845957a8 Sinan Kaya 2016-06-10 4124 /**
4d3f13845957a8 Sinan Kaya 2016-06-10 4125 * pci_unmap_iospace - Unmap the memory mapped I/O space
4d3f13845957a8 Sinan Kaya 2016-06-10 4126 * @res: resource to be unmapped
4d3f13845957a8 Sinan Kaya 2016-06-10 4127 *
74356addc0b32e Bjorn Helgaas 2019-01-09 4128 * Unmap the CPU virtual address @res from virtual address space. Only
74356addc0b32e Bjorn Helgaas 2019-01-09 4129 * architectures that have memory mapped IO functions defined (and the
74356addc0b32e Bjorn Helgaas 2019-01-09 4130 * PCI_IOBASE value defined) should call this function.
4d3f13845957a8 Sinan Kaya 2016-06-10 4131 */
4d3f13845957a8 Sinan Kaya 2016-06-10 4132 void pci_unmap_iospace(struct resource *res)
4d3f13845957a8 Sinan Kaya 2016-06-10 4133 {
8fe743b5eba0ab Arnd Bergmann 2025-04-23 4134 #if defined(PCI_IOBASE)
4d3f13845957a8 Sinan Kaya 2016-06-10 4135 unsigned long vaddr = (unsigned long)PCI_IOBASE + res->start;
4d3f13845957a8 Sinan Kaya 2016-06-10 4136
4ad0ae8c64ac8f Nicholas Piggin 2021-04-29 @4137 vunmap_range(vaddr, vaddr + resource_size(res));
4d3f13845957a8 Sinan Kaya 2016-06-10 4138 #endif
4d3f13845957a8 Sinan Kaya 2016-06-10 4139 }
f90b0875463e45 Brian Norris 2017-03-09 4140 EXPORT_SYMBOL(pci_unmap_iospace);
4d3f13845957a8 Sinan Kaya 2016-06-10 4141
:::::: The code at line 4137 was first introduced by commit
:::::: 4ad0ae8c64ac8f81a3651bca11be7c3cb086df80 mm/vmalloc: remove unmap_kernel_range
:::::: TO: Nicholas Piggin <npiggin@gmail.com>
:::::: CC: Linus Torvalds <torvalds@linux-foundation.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-09-27 4:12 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=202609270632.WSdFLSK0-lkp@intel.com \
--to=lkp@intel.com \
--cc=johannes.berg@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ricarkol@google.com \
--cc=thehajime@gmail.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