* [linux-next:master 12564/13831] kernel/dma/swiotlb.c:771:5: error: implicit declaration of function 'debugfs_create_dir'; did you mean 'kernfs_create_dir'?
@ 2021-06-28 18:00 kernel test robot
0 siblings, 0 replies; only message in thread
From: kernel test robot @ 2021-06-28 18:00 UTC (permalink / raw)
To: Claire Chang
Cc: kbuild-all, Linux Memory Management List, Konrad Rzeszutek Wilk,
Christoph Hellwig
[-- Attachment #1: Type: text/plain, Size: 3451 bytes --]
Hi Claire,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 3579aa488520feeda433ceca23ef4704bf8cd280
commit: 461021875c5057b3a408db0aa91b15119064ffa8 [12564/13831] swiotlb: Add restricted DMA pool initialization
config: h8300-randconfig-r004-20210628 (attached as .config)
compiler: h8300-linux-gcc (GCC) 9.3.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://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=461021875c5057b3a408db0aa91b15119064ffa8
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout 461021875c5057b3a408db0aa91b15119064ffa8
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=h8300
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
kernel/dma/swiotlb.c: In function 'rmem_swiotlb_device_init':
>> kernel/dma/swiotlb.c:771:5: error: implicit declaration of function 'debugfs_create_dir'; did you mean 'kernfs_create_dir'? [-Werror=implicit-function-declaration]
771 | debugfs_create_dir(rmem->name, debugfs_dir);
| ^~~~~~~~~~~~~~~~~~
| kernfs_create_dir
>> kernel/dma/swiotlb.c:771:36: error: 'debugfs_dir' undeclared (first use in this function)
771 | debugfs_create_dir(rmem->name, debugfs_dir);
| ^~~~~~~~~~~
kernel/dma/swiotlb.c:771:36: note: each undeclared identifier is reported only once for each function it appears in
>> kernel/dma/swiotlb.c:772:4: error: implicit declaration of function 'swiotlb_create_debugfs_files' [-Werror=implicit-function-declaration]
772 | swiotlb_create_debugfs_files(mem);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +771 kernel/dma/swiotlb.c
744
745 static int rmem_swiotlb_device_init(struct reserved_mem *rmem,
746 struct device *dev)
747 {
748 struct io_tlb_mem *mem = rmem->priv;
749 unsigned long nslabs = rmem->size >> IO_TLB_SHIFT;
750
751 /*
752 * Since multiple devices can share the same pool, the private data,
753 * io_tlb_mem struct, will be initialized by the first device attached
754 * to it.
755 */
756 if (!mem) {
757 mem = kzalloc(struct_size(mem, slots, nslabs), GFP_KERNEL);
758 if (!mem)
759 return -ENOMEM;
760
761 set_memory_decrypted((unsigned long)phys_to_virt(rmem->base),
762 rmem->size >> PAGE_SHIFT);
763 swiotlb_init_io_tlb_mem(mem, rmem->base, nslabs, false);
764 mem->force_bounce = true;
765 mem->for_alloc = true;
766
767 rmem->priv = mem;
768
769 if (IS_ENABLED(CONFIG_DEBUG_FS)) {
770 mem->debugfs =
> 771 debugfs_create_dir(rmem->name, debugfs_dir);
> 772 swiotlb_create_debugfs_files(mem);
773 }
774 }
775
776 dev->dma_io_tlb_mem = mem;
777
778 return 0;
779 }
780
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 35331 bytes --]
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2021-06-28 18:01 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-06-28 18:00 [linux-next:master 12564/13831] kernel/dma/swiotlb.c:771:5: error: implicit declaration of function 'debugfs_create_dir'; did you mean 'kernfs_create_dir'? kernel test robot
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox