From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [hch-misc:flush_icache_range 10/35] kernel/debug/debug_core.c:295:4: error: implicit declaration of function 'flush_cache_range'; did you mean 'flush_icache_range'?
Date: Sun, 10 May 2020 00:31:54 +0800 [thread overview]
Message-ID: <202005100046.0ND6AwMr%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4517 bytes --]
tree: git://git.infradead.org/users/hch/misc.git flush_icache_range
head: bc5fabce8570f28bcaabbca2fecaedb565a1933e
commit: 730ed167f78863c057b482b523de99d5ec278e21 [10/35] arm64: use asm-generic/cacheflush.h
config: arm64-allyesconfig (attached as .config)
compiler: aarch64-linux-gcc (GCC) 9.3.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 730ed167f78863c057b482b523de99d5ec278e21
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day GCC_VERSION=9.3.0 make.cross ARCH=arm64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
kernel/debug/debug_core.c: In function 'kgdb_flush_swbreak_addr':
>> kernel/debug/debug_core.c:295:4: error: implicit declaration of function 'flush_cache_range'; did you mean 'flush_icache_range'? [-Werror=implicit-function-declaration]
295 | flush_cache_range(current->vmacache.vmas[i],
| ^~~~~~~~~~~~~~~~~
| flush_icache_range
cc1: some warnings being treated as errors
--
kernel/events/uprobes.c: In function '__replace_page':
>> kernel/events/uprobes.c:203:2: error: implicit declaration of function 'flush_cache_page'; did you mean 'flush_dcache_page'? [-Werror=implicit-function-declaration]
203 | flush_cache_page(vma, addr, pte_pfn(*pvmw.pte));
| ^~~~~~~~~~~~~~~~
| flush_dcache_page
cc1: some warnings being treated as errors
vim +295 kernel/debug/debug_core.c
3cd99ac3559855 kernel/debug/debug_core.c Douglas Anderson 2018-12-04 279
dc7d552705215a kernel/kgdb.c Jason Wessel 2008-04-17 280 /*
dc7d552705215a kernel/kgdb.c Jason Wessel 2008-04-17 281 * Some architectures need cache flushes when we set/clear a
dc7d552705215a kernel/kgdb.c Jason Wessel 2008-04-17 282 * breakpoint:
dc7d552705215a kernel/kgdb.c Jason Wessel 2008-04-17 283 */
dc7d552705215a kernel/kgdb.c Jason Wessel 2008-04-17 284 static void kgdb_flush_swbreak_addr(unsigned long addr)
dc7d552705215a kernel/kgdb.c Jason Wessel 2008-04-17 285 {
dc7d552705215a kernel/kgdb.c Jason Wessel 2008-04-17 286 if (!CACHE_FLUSH_IS_SAFE)
dc7d552705215a kernel/kgdb.c Jason Wessel 2008-04-17 287 return;
dc7d552705215a kernel/kgdb.c Jason Wessel 2008-04-17 288
615d6e8756c871 kernel/debug/debug_core.c Davidlohr Bueso 2014-04-07 289 if (current->mm) {
615d6e8756c871 kernel/debug/debug_core.c Davidlohr Bueso 2014-04-07 290 int i;
615d6e8756c871 kernel/debug/debug_core.c Davidlohr Bueso 2014-04-07 291
615d6e8756c871 kernel/debug/debug_core.c Davidlohr Bueso 2014-04-07 292 for (i = 0; i < VMACACHE_SIZE; i++) {
314ff7851fc8ea kernel/debug/debug_core.c Ingo Molnar 2017-02-03 293 if (!current->vmacache.vmas[i])
615d6e8756c871 kernel/debug/debug_core.c Davidlohr Bueso 2014-04-07 294 continue;
314ff7851fc8ea kernel/debug/debug_core.c Ingo Molnar 2017-02-03 @295 flush_cache_range(current->vmacache.vmas[i],
dc7d552705215a kernel/kgdb.c Jason Wessel 2008-04-17 296 addr, addr + BREAK_INSTR_SIZE);
dc7d552705215a kernel/kgdb.c Jason Wessel 2008-04-17 297 }
615d6e8756c871 kernel/debug/debug_core.c Davidlohr Bueso 2014-04-07 298 }
615d6e8756c871 kernel/debug/debug_core.c Davidlohr Bueso 2014-04-07 299
1a9a3e76dde191 kernel/kgdb.c Jason Wessel 2008-04-01 300 /* Force flush instruction cache if it was outside the mm */
1a9a3e76dde191 kernel/kgdb.c Jason Wessel 2008-04-01 301 flush_icache_range(addr, addr + BREAK_INSTR_SIZE);
dc7d552705215a kernel/kgdb.c Jason Wessel 2008-04-17 302 }
dc7d552705215a kernel/kgdb.c Jason Wessel 2008-04-17 303
:::::: The code at line 295 was first introduced by commit
:::::: 314ff7851fc8ea66cbf48eaa93d8ebfb5ca084a9 mm/vmacache, sched/headers: Introduce 'struct vmacache' and move it from <linux/sched.h> to <linux/mm_types>
:::::: TO: Ingo Molnar <mingo@kernel.org>
:::::: CC: Ingo Molnar <mingo@kernel.org>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 71796 bytes --]
reply other threads:[~2020-05-09 16:31 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=202005100046.0ND6AwMr%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.