From: kernel test robot <lkp@intel.com>
To: Nam Cao <namcao@linutronix.de>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
"Thomas Weißschuh " <thomas.weissschuh@linutronix.de>
Subject: [thomas-weissschuh:b4/riscv-vdso32-alternative 5/9] arch/riscv/kernel/vdso.c:78:53: error: use of undeclared identifier '__vdso_futex_list64_try_unlock_cs_lrsc_start_offset'
Date: Tue, 30 Jun 2026 18:53:26 +0800 [thread overview]
Message-ID: <202606301855.WvkSC4kD-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/thomas.weissschuh/linux.git b4/riscv-vdso32-alternative
head: a8d7e9eb82942f57e8a56aa6f2189a32ddf87667
commit: 10cd4cf20d3d92532485e3f0384e61abc90d6c54 [5/9] riscv: vdso: Implement __vdso_futex_robust_try_unlock()
config: riscv-randconfig-001-20260630 (https://download.01.org/0day-ci/archive/20260630/202606301855.WvkSC4kD-lkp@intel.com/config)
compiler: clang version 23.0.0git (https://github.com/llvm/llvm-project 6cc609bb250b21b47fc7d394b4019101e9983597)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260630/202606301855.WvkSC4kD-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/202606301855.WvkSC4kD-lkp@intel.com/
All errors (new ones prefixed by >>):
>> arch/riscv/kernel/vdso.c:78:53: error: use of undeclared identifier '__vdso_futex_list64_try_unlock_cs_lrsc_start_offset'
78 | FUTEX_SET_VDSO_CS_RANGE(vdso, fd, 0, __riscv_xlen, __VDSO_SYMBOL);
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~
arch/riscv/kernel/vdso.c:56:16: note: expanded from macro 'FUTEX_SET_VDSO_CS_RANGE'
56 | void *start = symbol(vdso, CONCAT3(futex_list, xlen, _try_unlock_cs_lrsc_start)); \
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
arch/riscv/kernel/vdso.c:68:36: note: expanded from macro '__VDSO_SYMBOL'
68 | #define __VDSO_SYMBOL(vdso, name) VDSO_SYMBOL(vdso, name)
| ^~~~~~~~~~~~~~~~~~~~~~~
arch/riscv/include/asm/vdso.h:35:45: note: expanded from macro 'VDSO_SYMBOL'
35 | ((void __user *)((unsigned long)(base) + __vdso_##name##_offset))
| ^~~~~~~~~~~~~~~~~~~~~~
<scratch space>:128:1: note: expanded from here
128 | __vdso_futex_list64_try_unlock_cs_lrsc_start_offset
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> arch/riscv/kernel/vdso.c:78:53: error: use of undeclared identifier '__vdso_futex_list64_try_unlock_cs_lrsc_end_offset'
78 | FUTEX_SET_VDSO_CS_RANGE(vdso, fd, 0, __riscv_xlen, __VDSO_SYMBOL);
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~
arch/riscv/kernel/vdso.c:57:16: note: expanded from macro 'FUTEX_SET_VDSO_CS_RANGE'
57 | void *end = symbol(vdso, CONCAT3(futex_list, xlen, _try_unlock_cs_lrsc_end)); \
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
arch/riscv/kernel/vdso.c:68:36: note: expanded from macro '__VDSO_SYMBOL'
68 | #define __VDSO_SYMBOL(vdso, name) VDSO_SYMBOL(vdso, name)
| ^~~~~~~~~~~~~~~~~~~~~~~
arch/riscv/include/asm/vdso.h:35:45: note: expanded from macro 'VDSO_SYMBOL'
35 | ((void __user *)((unsigned long)(base) + __vdso_##name##_offset))
| ^~~~~~~~~~~~~~~~~~~~~~
<scratch space>:132:1: note: expanded from here
132 | __vdso_futex_list64_try_unlock_cs_lrsc_end_offset
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2 errors generated.
vim +/__vdso_futex_list64_try_unlock_cs_lrsc_start_offset +78 arch/riscv/kernel/vdso.c
70
71 static void vdso_futex_robust_unlock_update_ips(void)
72 {
73 unsigned long vdso = (unsigned long) current->mm->context.vdso;
74 struct futex_mm_data *fd = ¤t->mm->futex;
75
76 futex_reset_cs_ranges(fd);
77
> 78 FUTEX_SET_VDSO_CS_RANGE(vdso, fd, 0, __riscv_xlen, __VDSO_SYMBOL);
79
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-06-30 10:53 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=202606301855.WvkSC4kD-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=namcao@linutronix.de \
--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 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.