Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Melon Liu <melon1335@163.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	"Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>,
	Linus Walleij <linus.walleij@linaro.org>
Subject: [rmk:for-next 3/7] arch/arm/mm/ioremap.c:130:32: error: call to undeclared function 'kasan_mem_to_shadow'; ISO C99 and later do not support implicit function declarations
Date: Wed, 13 Nov 2024 07:10:39 +0800	[thread overview]
Message-ID: <202411130711.xfVEiMKn-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/rmk/linux.git for-next
head:   315cfa0efa30b8f1c9b8d6b8b5cc9e6c337906ff
commit: 15c0b4cb0223a5cf9783e3759be115c1ca643368 [3/7] ARM: 9427/1: mm: Fix stack recursion caused by KASAN
config: arm-integrator_defconfig (https://download.01.org/0day-ci/archive/20241113/202411130711.xfVEiMKn-lkp@intel.com/config)
compiler: clang version 20.0.0git (https://github.com/llvm/llvm-project 592c0fe55f6d9a811028b5f3507be91458ab2713)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241113/202411130711.xfVEiMKn-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/202411130711.xfVEiMKn-lkp@intel.com/

All errors (new ones prefixed by >>):

   In file included from arch/arm/mm/ioremap.c:26:
   In file included from include/linux/mm.h:2213:
   include/linux/vmstat.h:518:36: warning: arithmetic between different enumeration types ('enum node_stat_item' and 'enum lru_list') [-Wenum-enum-conversion]
     518 |         return node_stat_name(NR_LRU_BASE + lru) + 3; // skip "nr_"
         |                               ~~~~~~~~~~~ ^ ~~~
>> arch/arm/mm/ioremap.c:130:32: error: call to undeclared function 'kasan_mem_to_shadow'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
     130 |                 sync_pgds(mm, (unsigned long)kasan_mem_to_shadow(
         |                                              ^
   1 warning and 1 error generated.


vim +/kasan_mem_to_shadow +130 arch/arm/mm/ioremap.c

   125	
   126	static inline void sync_vmalloc_pgds(struct mm_struct *mm)
   127	{
   128		sync_pgds(mm, VMALLOC_START, VMALLOC_END);
   129		if (IS_ENABLED(CONFIG_KASAN_VMALLOC))
 > 130			sync_pgds(mm, (unsigned long)kasan_mem_to_shadow(
   131						(void *)VMALLOC_START),
   132				      (unsigned long)kasan_mem_to_shadow(
   133						(void *)VMALLOC_END));
   134	}
   135	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

             reply	other threads:[~2024-11-12 23:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-12 23:10 kernel test robot [this message]
2024-11-13  0:34 ` [rmk:for-next 3/7] arch/arm/mm/ioremap.c:130:32: error: call to undeclared function 'kasan_mem_to_shadow'; ISO C99 and later do not support implicit function declarations Linus Walleij
2024-11-13 14:20   ` Russell King (Oracle)
2024-11-14  7:40     ` Linus Walleij

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=202411130711.xfVEiMKn-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=linus.walleij@linaro.org \
    --cc=llvm@lists.linux.dev \
    --cc=melon1335@163.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=rmk+kernel@armlinux.org.uk \
    /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