From: kernel test robot <lkp@intel.com>
To: Pasha Tatashin <pasha.tatashin@soleen.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Linus Walleij <linusw@kernel.org>
Subject: [arm-integrator:b4/aarch64-dynamic-kernel-stacks-v7.0-rc1 7/13] kernel/fork.c:260:28: error: use of undeclared identifier 'THREAD_PREALLOC_PAGES'
Date: Fri, 13 Mar 2026 08:09:35 +0100 [thread overview]
Message-ID: <202603130843.MyLfc9hR-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-integrator.git b4/aarch64-dynamic-kernel-stacks-v7.0-rc1
head: 3ea8b0381a0759fa0c71abae5274db2414b58e78
commit: d2ee0928bdd182aed09a1eabb9c008eef73bb442 [7/13] fork: Dynamic Kernel Stacks
config: x86_64-kexec (https://download.01.org/0day-ci/archive/20260313/202603130843.MyLfc9hR-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260313/202603130843.MyLfc9hR-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/202603130843.MyLfc9hR-lkp@intel.com/
All errors (new ones prefixed by >>):
>> kernel/fork.c:260:28: error: use of undeclared identifier 'THREAD_PREALLOC_PAGES'
260 | if (vm_area->nr_pages > THREAD_PREALLOC_PAGES)
| ^
1 error generated.
vim +/THREAD_PREALLOC_PAGES +260 kernel/fork.c
238
239 static bool try_release_thread_stack_to_cache(struct vm_struct *vm_area)
240 {
241 unsigned int i;
242 int nid;
243
244 /*
245 * Don't cache stacks if any of the pages don't match the local domain, unless
246 * there is no local memory to begin with.
247 *
248 * Note that lack of local memory does not automatically mean it makes no difference
249 * performance-wise which other domain backs the stack. In this case we are merely
250 * trying to avoid constantly going to vmalloc.
251 */
252 scoped_guard(preempt) {
253 if (IS_ENABLED(CONFIG_DYNAMIC_STACK)) {
254 /*
255 * If we have faulted in more than the default number of
256 * stack pages to a stack, don't re-use it. This makes sure
257 * a process never use more than THREAD_PREALLOC_PAGES
258 * at the outset.
259 */
> 260 if (vm_area->nr_pages > THREAD_PREALLOC_PAGES)
261 return false;
262 }
263 nid = numa_node_id();
264 if (node_state(nid, N_MEMORY)) {
265 for (i = 0; i < vm_area->nr_pages; i++) {
266 struct page *page = vm_area->pages[i];
267 if (page_to_nid(page) != nid)
268 return false;
269 }
270 }
271
272 for (i = 0; i < NR_CACHED_STACKS; i++) {
273 struct vm_struct *tmp = NULL;
274
275 if (this_cpu_try_cmpxchg(cached_stacks[i], &tmp, vm_area))
276 return true;
277 }
278 }
279 return false;
280 }
281
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-03-13 7:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 7:09 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-16 5:35 [arm-integrator:b4/aarch64-dynamic-kernel-stacks-v7.0-rc1 7/13] kernel/fork.c:260:28: error: use of undeclared identifier 'THREAD_PREALLOC_PAGES' kernel test robot
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=202603130843.MyLfc9hR-lkp@intel.com \
--to=lkp@intel.com \
--cc=linusw@kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pasha.tatashin@soleen.com \
/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