From: kernel test robot <lkp@intel.com>
To: Austin Kim <austindh.kim@gmail.com>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Alexandre Ghiti <alex@ghiti.fr>,
Albert Ou <aou@eecs.berkeley.edu>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, austindh.kim@gmail.com
Subject: Re: [PATCH] riscv: export kaslr offset and satp in VMCOREINFO ELF notes
Date: Tue, 27 Jan 2026 20:13:41 +0100 [thread overview]
Message-ID: <202601272006.NUdRcAIi-lkp@intel.com> (raw)
In-Reply-To: <aXiF55y5D49gcpUg@adminpc-PowerEdge-R7525>
Hi Austin,
kernel test robot noticed the following build errors:
[auto build test ERROR on linus/master]
[also build test ERROR on v6.16-rc1 next-20260127]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Austin-Kim/riscv-export-kaslr-offset-and-satp-in-VMCOREINFO-ELF-notes/20260127-173528
base: linus/master
patch link: https://lore.kernel.org/r/aXiF55y5D49gcpUg%40adminpc-PowerEdge-R7525
patch subject: [PATCH] riscv: export kaslr offset and satp in VMCOREINFO ELF notes
config: riscv-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20260127/202601272006.NUdRcAIi-lkp@intel.com/config)
compiler: riscv64-linux-gcc (GCC) 15.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260127/202601272006.NUdRcAIi-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/202601272006.NUdRcAIi-lkp@intel.com/
All errors (new ones prefixed by >>):
riscv64-linux-ld: arch/riscv/kernel/vmcore_info.o: in function `arch_crash_save_vmcoreinfo':
>> arch/riscv/kernel/vmcore_info.c:23:(.text+0x240): undefined reference to `kaslr_offset'
vim +23 arch/riscv/kernel/vmcore_info.c
cfe94d456775a4 arch/riscv/kernel/vmcore_info.c Austin Kim 2026-01-27 10
649d6b1019a2f2 arch/riscv/kernel/crash_core.c Xianting Tian 2022-10-26 11 void arch_crash_save_vmcoreinfo(void)
649d6b1019a2f2 arch/riscv/kernel/crash_core.c Xianting Tian 2022-10-26 12 {
649d6b1019a2f2 arch/riscv/kernel/crash_core.c Xianting Tian 2022-10-26 13 VMCOREINFO_NUMBER(phys_ram_base);
649d6b1019a2f2 arch/riscv/kernel/crash_core.c Xianting Tian 2022-10-26 14
649d6b1019a2f2 arch/riscv/kernel/crash_core.c Xianting Tian 2022-10-26 15 vmcoreinfo_append_str("NUMBER(PAGE_OFFSET)=0x%lx\n", PAGE_OFFSET);
649d6b1019a2f2 arch/riscv/kernel/crash_core.c Xianting Tian 2022-10-26 16 vmcoreinfo_append_str("NUMBER(VMALLOC_END)=0x%lx\n", VMALLOC_END);
c41bd2514184d7 arch/riscv/kernel/crash_core.c Ignat Korchagin 2023-11-29 17 #ifdef CONFIG_MMU
c41bd2514184d7 arch/riscv/kernel/crash_core.c Ignat Korchagin 2023-11-29 18 VMCOREINFO_NUMBER(VA_BITS);
649d6b1019a2f2 arch/riscv/kernel/crash_core.c Xianting Tian 2022-10-26 19 vmcoreinfo_append_str("NUMBER(VMEMMAP_START)=0x%lx\n", VMEMMAP_START);
649d6b1019a2f2 arch/riscv/kernel/crash_core.c Xianting Tian 2022-10-26 20 vmcoreinfo_append_str("NUMBER(VMEMMAP_END)=0x%lx\n", VMEMMAP_END);
649d6b1019a2f2 arch/riscv/kernel/crash_core.c Xianting Tian 2022-10-26 21 #ifdef CONFIG_64BIT
649d6b1019a2f2 arch/riscv/kernel/crash_core.c Xianting Tian 2022-10-26 22 vmcoreinfo_append_str("NUMBER(MODULES_VADDR)=0x%lx\n", MODULES_VADDR);
649d6b1019a2f2 arch/riscv/kernel/crash_core.c Xianting Tian 2022-10-26 @23 vmcoreinfo_append_str("NUMBER(MODULES_END)=0x%lx\n", MODULES_END);
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-01-27 19:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 9:31 [PATCH] riscv: export kaslr offset and satp in VMCOREINFO ELF notes Austin Kim
2026-01-27 19:13 ` kernel test robot [this message]
2026-01-28 10:36 ` Austin Kim
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=202601272006.NUdRcAIi-lkp@intel.com \
--to=lkp@intel.com \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=austindh.kim@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox