From: kernel test robot <lkp@intel.com>
To: "Thomas Weißschuh " <thomas.weissschuh@linutronix.de>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [thomas-weissschuh:b4/riscv-cfi-vdso-alternative 2/4] arch/riscv/kernel/alternative.c:183:20: error: use of undeclared identifier 'vdso_start'
Date: Thu, 30 Apr 2026 11:55:31 +0800 [thread overview]
Message-ID: <202604301147.qlAxtlut-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/thomas.weissschuh/linux.git b4/riscv-cfi-vdso-alternative
head: fa83dca7c15f5aefda0432bda4aa4a802766ca70
commit: 45f16afdf0331f9d95eac2a3d328f715fbe316bb [2/4] riscv: alternative: Replace ifdeffery around apply_vdso_alternatives() with IS_ENABLED()
config: riscv-randconfig-001-20260430 (https://download.01.org/0day-ci/archive/20260430/202604301147.qlAxtlut-lkp@intel.com/config)
compiler: clang version 23.0.0git (https://github.com/llvm/llvm-project 5bac06718f502014fade905512f1d26d578a18f3)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260430/202604301147.qlAxtlut-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/202604301147.qlAxtlut-lkp@intel.com/
All errors (new ones prefixed by >>):
>> arch/riscv/kernel/alternative.c:183:20: error: use of undeclared identifier 'vdso_start'
183 | hdr = (Elf_Ehdr *)vdso_start;
| ^~~~~~~~~~
1 error generated.
vim +/vdso_start +183 arch/riscv/kernel/alternative.c
d14ca1f8d30399 Heiko Stuebner 2022-05-11 175
cabfd146b37146 Jisheng Zhang 2023-01-29 176 static void __init apply_vdso_alternatives(void)
cabfd146b37146 Jisheng Zhang 2023-01-29 177 {
cabfd146b37146 Jisheng Zhang 2023-01-29 178 const Elf_Ehdr *hdr;
cabfd146b37146 Jisheng Zhang 2023-01-29 179 const Elf_Shdr *shdr;
cabfd146b37146 Jisheng Zhang 2023-01-29 180 const Elf_Shdr *alt;
cabfd146b37146 Jisheng Zhang 2023-01-29 181 struct alt_entry *begin, *end;
cabfd146b37146 Jisheng Zhang 2023-01-29 182
cabfd146b37146 Jisheng Zhang 2023-01-29 @183 hdr = (Elf_Ehdr *)vdso_start;
cabfd146b37146 Jisheng Zhang 2023-01-29 184 shdr = (void *)hdr + hdr->e_shoff;
cabfd146b37146 Jisheng Zhang 2023-01-29 185 alt = find_section(hdr, shdr, ".alternative");
cabfd146b37146 Jisheng Zhang 2023-01-29 186 if (!alt)
cabfd146b37146 Jisheng Zhang 2023-01-29 187 return;
cabfd146b37146 Jisheng Zhang 2023-01-29 188
cabfd146b37146 Jisheng Zhang 2023-01-29 189 begin = (void *)hdr + alt->sh_offset,
cabfd146b37146 Jisheng Zhang 2023-01-29 190 end = (void *)hdr + alt->sh_offset + alt->sh_size,
cabfd146b37146 Jisheng Zhang 2023-01-29 191
cabfd146b37146 Jisheng Zhang 2023-01-29 192 _apply_alternatives((struct alt_entry *)begin,
cabfd146b37146 Jisheng Zhang 2023-01-29 193 (struct alt_entry *)end,
cabfd146b37146 Jisheng Zhang 2023-01-29 194 RISCV_ALTERNATIVES_BOOT);
cabfd146b37146 Jisheng Zhang 2023-01-29 195 }
cabfd146b37146 Jisheng Zhang 2023-01-29 196
:::::: The code at line 183 was first introduced by commit
:::::: cabfd146b371462ed480a968f98eb0c2c80e3c8a riscv: alternative: patch alternatives in the vDSO
:::::: TO: Jisheng Zhang <jszhang@kernel.org>
:::::: CC: Palmer Dabbelt <palmer@rivosinc.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-04-30 3:55 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=202604301147.qlAxtlut-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=thomas.weissschuh@linutronix.de \
/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