From: kernel test robot <lkp@intel.com>
To: Eric DeVolder <eric.devolder@oracle.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [linux-next:master 12990/13166] arch/riscv/kernel/crash_core.c:8:27: error: 'VA_BITS' undeclared
Date: Wed, 5 Jul 2023 00:34:55 +0800 [thread overview]
Message-ID: <202307050034.tAJSN9qy-lkp@intel.com> (raw)
Hi Eric,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 1c6f93977947dbba1fc4d250c4eb8a7d4cfdecf1
commit: 8d14224263d97d0d53061cf08c2fa911418b1b7f [12990/13166] riscv/kexec: refactor for kernel/Kconfig.kexec
config: riscv-randconfig-r014-20230704 (https://download.01.org/0day-ci/archive/20230705/202307050034.tAJSN9qy-lkp@intel.com/config)
compiler: riscv64-linux-gcc (GCC) 12.3.0
reproduce: (https://download.01.org/0day-ci/archive/20230705/202307050034.tAJSN9qy-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/202307050034.tAJSN9qy-lkp@intel.com/
Note: the linux-next/master HEAD 1c6f93977947dbba1fc4d250c4eb8a7d4cfdecf1 builds fine.
It may have been fixed somewhere.
All errors (new ones prefixed by >>):
In file included from arch/riscv/kernel/crash_core.c:3:
arch/riscv/kernel/crash_core.c: In function 'arch_crash_save_vmcoreinfo':
>> arch/riscv/kernel/crash_core.c:8:27: error: 'VA_BITS' undeclared (first use in this function)
8 | VMCOREINFO_NUMBER(VA_BITS);
| ^~~~~~~
include/linux/crash_core.h:68:64: note: in definition of macro 'VMCOREINFO_NUMBER'
68 | vmcoreinfo_append_str("NUMBER(%s)=%ld\n", #name, (long)name)
| ^~~~
arch/riscv/kernel/crash_core.c:8:27: note: each undeclared identifier is reported only once for each function it appears in
8 | VMCOREINFO_NUMBER(VA_BITS);
| ^~~~~~~
include/linux/crash_core.h:68:64: note: in definition of macro 'VMCOREINFO_NUMBER'
68 | vmcoreinfo_append_str("NUMBER(%s)=%ld\n", #name, (long)name)
| ^~~~
arch/riscv/kernel/crash_core.c:12:58: warning: format '%lx' expects argument of type 'long unsigned int', but argument 2 has type 'int' [-Wformat=]
12 | vmcoreinfo_append_str("NUMBER(VMALLOC_START)=0x%lx\n", VMALLOC_START);
| ~~^
| |
| long unsigned int
| %x
>> arch/riscv/kernel/crash_core.c:14:64: error: 'VMEMMAP_START' undeclared (first use in this function)
14 | vmcoreinfo_append_str("NUMBER(VMEMMAP_START)=0x%lx\n", VMEMMAP_START);
| ^~~~~~~~~~~~~
>> arch/riscv/kernel/crash_core.c:15:62: error: 'VMEMMAP_END' undeclared (first use in this function); did you mean 'MEMREMAP_ENC'?
15 | vmcoreinfo_append_str("NUMBER(VMEMMAP_END)=0x%lx\n", VMEMMAP_END);
| ^~~~~~~~~~~
| MEMREMAP_ENC
>> arch/riscv/kernel/crash_core.c:17:64: error: 'MODULES_VADDR' undeclared (first use in this function)
17 | vmcoreinfo_append_str("NUMBER(MODULES_VADDR)=0x%lx\n", MODULES_VADDR);
| ^~~~~~~~~~~~~
>> arch/riscv/kernel/crash_core.c:18:62: error: 'MODULES_END' undeclared (first use in this function)
18 | vmcoreinfo_append_str("NUMBER(MODULES_END)=0x%lx\n", MODULES_END);
| ^~~~~~~~~~~
vim +/VA_BITS +8 arch/riscv/kernel/crash_core.c
649d6b1019a2f2 Xianting Tian 2022-10-26 5
649d6b1019a2f2 Xianting Tian 2022-10-26 6 void arch_crash_save_vmcoreinfo(void)
649d6b1019a2f2 Xianting Tian 2022-10-26 7 {
649d6b1019a2f2 Xianting Tian 2022-10-26 @8 VMCOREINFO_NUMBER(VA_BITS);
649d6b1019a2f2 Xianting Tian 2022-10-26 9 VMCOREINFO_NUMBER(phys_ram_base);
649d6b1019a2f2 Xianting Tian 2022-10-26 10
649d6b1019a2f2 Xianting Tian 2022-10-26 11 vmcoreinfo_append_str("NUMBER(PAGE_OFFSET)=0x%lx\n", PAGE_OFFSET);
649d6b1019a2f2 Xianting Tian 2022-10-26 12 vmcoreinfo_append_str("NUMBER(VMALLOC_START)=0x%lx\n", VMALLOC_START);
649d6b1019a2f2 Xianting Tian 2022-10-26 13 vmcoreinfo_append_str("NUMBER(VMALLOC_END)=0x%lx\n", VMALLOC_END);
649d6b1019a2f2 Xianting Tian 2022-10-26 @14 vmcoreinfo_append_str("NUMBER(VMEMMAP_START)=0x%lx\n", VMEMMAP_START);
649d6b1019a2f2 Xianting Tian 2022-10-26 @15 vmcoreinfo_append_str("NUMBER(VMEMMAP_END)=0x%lx\n", VMEMMAP_END);
649d6b1019a2f2 Xianting Tian 2022-10-26 16 #ifdef CONFIG_64BIT
649d6b1019a2f2 Xianting Tian 2022-10-26 @17 vmcoreinfo_append_str("NUMBER(MODULES_VADDR)=0x%lx\n", MODULES_VADDR);
649d6b1019a2f2 Xianting Tian 2022-10-26 @18 vmcoreinfo_append_str("NUMBER(MODULES_END)=0x%lx\n", MODULES_END);
:::::: The code at line 8 was first introduced by commit
:::::: 649d6b1019a2f243bc3a98cb85902a8ebf74289a RISC-V: Add arch_crash_save_vmcoreinfo support
:::::: TO: Xianting Tian <xianting.tian@linux.alibaba.com>
:::::: CC: Palmer Dabbelt <palmer@rivosinc.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-07-04 16:35 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=202307050034.tAJSN9qy-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=eric.devolder@oracle.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