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 4/4] arch/riscv/kernel/alternative.c:210:27: error: use of undeclared identifier 'vdso_cfi_start'
Date: Thu, 30 Apr 2026 14:10:01 +0800 [thread overview]
Message-ID: <202604301435.3ApdMPjV-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: fa83dca7c15f5aefda0432bda4aa4a802766ca70 [4/4] riscv: alternative: Also patch the CFI vDSO
config: riscv-randconfig-001-20260430 (https://download.01.org/0day-ci/archive/20260430/202604301435.3ApdMPjV-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/202604301435.3ApdMPjV-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/202604301435.3ApdMPjV-lkp@intel.com/
All errors (new ones prefixed by >>):
arch/riscv/kernel/alternative.c:207:27: error: use of undeclared identifier 'vdso_start'; did you mean 'vfs_stat'?
207 | apply_vdso_alternatives(vdso_start);
| ^~~~~~~~~~
| vfs_stat
include/linux/fs.h:3206:19: note: 'vfs_stat' declared here
3206 | static inline int vfs_stat(const char __user *filename, struct kstat *stat)
| ^
>> arch/riscv/kernel/alternative.c:210:27: error: use of undeclared identifier 'vdso_cfi_start'
210 | apply_vdso_alternatives(vdso_cfi_start);
| ^~~~~~~~~~~~~~
2 errors generated.
vim +/vdso_cfi_start +210 arch/riscv/kernel/alternative.c
196
197 void __init apply_boot_alternatives(void)
198 {
199 /* If called on non-boot cpu things could go wrong */
200 WARN_ON(smp_processor_id() != 0);
201
202 _apply_alternatives((struct alt_entry *)__alt_start,
203 (struct alt_entry *)__alt_end,
204 RISCV_ALTERNATIVES_BOOT);
205
206 if (IS_ENABLED(CONFIG_MMU))
207 apply_vdso_alternatives(vdso_start);
208
209 if (IS_ENABLED(CONFIG_RISCV_USER_CFI))
> 210 apply_vdso_alternatives(vdso_cfi_start);
211 }
212
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-04-30 6:10 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=202604301435.3ApdMPjV-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