From: kernel test robot <lkp@intel.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, Mark Brown <broonie@kernel.org>
Subject: [linux-next:master 10288/10352] kernel/time/namespace_vdso.c:137:25: error: implicit declaration of function 'zap_vma_pages'; did you mean 'zap_vma_range'?
Date: Tue, 31 Mar 2026 22:22:20 +0800 [thread overview]
Message-ID: <202603312208.QNLATFuj-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: cf7c3c02fdd0dfccf4d6611714273dcb538af2cb
commit: e0aa1be6ed33eb71b3e2783e9b1f3204f4e42600 [10288/10352] Merge branch 'master' of https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
config: x86_64-rhel-9.4 (https://download.01.org/0day-ci/archive/20260331/202603312208.QNLATFuj-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260331/202603312208.QNLATFuj-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/202603312208.QNLATFuj-lkp@intel.com/
Note: the linux-next/master HEAD cf7c3c02fdd0dfccf4d6611714273dcb538af2cb builds fine.
It may have been fixed somewhere.
All errors (new ones prefixed by >>):
kernel/time/namespace_vdso.c: In function 'vdso_join_timens':
>> kernel/time/namespace_vdso.c:137:25: error: implicit declaration of function 'zap_vma_pages'; did you mean 'zap_vma_range'? [-Wimplicit-function-declaration]
137 | zap_vma_pages(vma);
| ^~~~~~~~~~~~~
| zap_vma_range
vim +137 kernel/time/namespace_vdso.c
5dc9cf835aba73 Thomas Weißschuh 2026-03-26 120
5dc9cf835aba73 Thomas Weißschuh 2026-03-26 121 /*
5dc9cf835aba73 Thomas Weißschuh 2026-03-26 122 * The vvar page layout depends on whether a task belongs to the root or
5dc9cf835aba73 Thomas Weißschuh 2026-03-26 123 * non-root time namespace. Whenever a task changes its namespace, the VVAR
5dc9cf835aba73 Thomas Weißschuh 2026-03-26 124 * page tables are cleared and then they will be re-faulted with a
5dc9cf835aba73 Thomas Weißschuh 2026-03-26 125 * corresponding layout.
5dc9cf835aba73 Thomas Weißschuh 2026-03-26 126 * See also the comment near timens_setup_vdso_clock_data() for details.
5dc9cf835aba73 Thomas Weißschuh 2026-03-26 127 */
5dc9cf835aba73 Thomas Weißschuh 2026-03-26 128 static int vdso_join_timens(struct task_struct *task, struct time_namespace *ns)
5dc9cf835aba73 Thomas Weißschuh 2026-03-26 129 {
5dc9cf835aba73 Thomas Weißschuh 2026-03-26 130 struct mm_struct *mm = task->mm;
5dc9cf835aba73 Thomas Weißschuh 2026-03-26 131 struct vm_area_struct *vma;
5dc9cf835aba73 Thomas Weißschuh 2026-03-26 132 VMA_ITERATOR(vmi, mm, 0);
5dc9cf835aba73 Thomas Weißschuh 2026-03-26 133
5dc9cf835aba73 Thomas Weißschuh 2026-03-26 134 guard(mmap_read_lock)(mm);
5dc9cf835aba73 Thomas Weißschuh 2026-03-26 135 for_each_vma(vmi, vma) {
5dc9cf835aba73 Thomas Weißschuh 2026-03-26 136 if (vma_is_special_mapping(vma, &vdso_vvar_mapping))
5dc9cf835aba73 Thomas Weißschuh 2026-03-26 @137 zap_vma_pages(vma);
5dc9cf835aba73 Thomas Weißschuh 2026-03-26 138 }
5dc9cf835aba73 Thomas Weißschuh 2026-03-26 139 return 0;
5dc9cf835aba73 Thomas Weißschuh 2026-03-26 140 }
5dc9cf835aba73 Thomas Weißschuh 2026-03-26 141
:::::: The code at line 137 was first introduced by commit
:::::: 5dc9cf835aba73c882348aa4f99be83b6e45ad9b vdso/timens: Move functions to new file
:::::: TO: Thomas Weißschuh <thomas.weissschuh@linutronix.de>
:::::: CC: Thomas Gleixner <tglx@kernel.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-03-31 14:22 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=202603312208.QNLATFuj-lkp@intel.com \
--to=lkp@intel.com \
--cc=broonie@kernel.org \
--cc=mingo@kernel.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 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.