[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <202511220009.u6dJXVkB-lkp@intel.com>
Date: Sat, 22 Nov 2025 01:13:52 +0800
From: kernel test robot <lkp@...el.com>
To: Eugen Hristev <eugen.hristev@...aro.org>, linux-arm-msm@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
tglx@...utronix.de, andersson@...nel.org, pmladek@...e.com,
rdunlap@...radead.org, corbet@....net, david@...hat.com,
mhocko@...e.com
Cc: oe-kbuild-all@...ts.linux.dev, tudor.ambarus@...aro.org,
mukesh.ojha@....qualcomm.com, linux-arm-kernel@...ts.infradead.org,
linux-hardening@...r.kernel.org, jonechou@...gle.com,
rostedt@...dmis.org, linux-doc@...r.kernel.org,
devicetree@...r.kernel.org, linux-remoteproc@...r.kernel.org,
linux-arch@...r.kernel.org, tony.luck@...el.com, kees@...nel.org,
Eugen Hristev <eugen.hristev@...aro.org>
Subject: Re: [PATCH 03/26] mm/percpu: Annotate static information into
meminspect
Hi Eugen,
kernel test robot noticed the following build errors:
[auto build test ERROR on rppt-memblock/fixes]
[also build test ERROR on linus/master v6.18-rc6]
[cannot apply to akpm-mm/mm-everything rppt-memblock/for-next next-20251121]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Eugen-Hristev/kernel-Introduce-meminspect/20251119-235912
base: https://git.kernel.org/pub/scm/linux/kernel/git/rppt/memblock.git fixes
patch link: https://lore.kernel.org/r/20251119154427.1033475-4-eugen.hristev%40linaro.org
patch subject: [PATCH 03/26] mm/percpu: Annotate static information into meminspect
config: nios2-allmodconfig (https://download.01.org/0day-ci/archive/20251122/202511220009.u6dJXVkB-lkp@intel.com/config)
compiler: nios2-linux-gcc (GCC) 11.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251122/202511220009.u6dJXVkB-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@...el.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202511220009.u6dJXVkB-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from mm/percpu.c:90:
>> mm/percpu.c:3350:25: error: '__per_cpu_offset' undeclared here (not in a function); did you mean '__per_cpu_start'?
3350 | MEMINSPECT_SIMPLE_ENTRY(__per_cpu_offset);
| ^~~~~~~~~~~~~~~~
include/linux/meminspect.h:92:64: note: in definition of macro 'MEMINSPECT_ENTRY'
92 | .va = (void *)&(sym), \
| ^~~
mm/percpu.c:3350:1: note: in expansion of macro 'MEMINSPECT_SIMPLE_ENTRY'
3350 | MEMINSPECT_SIMPLE_ENTRY(__per_cpu_offset);
| ^~~~~~~~~~~~~~~~~~~~~~~
vim +3350 mm/percpu.c
3349
> 3350 MEMINSPECT_SIMPLE_ENTRY(__per_cpu_offset);
3351 /*
3352 * pcpu_nr_pages - calculate total number of populated backing pages
3353 *
3354 * This reflects the number of pages populated to back chunks. Metadata is
3355 * excluded in the number exposed in meminfo as the number of backing pages
3356 * scales with the number of cpus and can quickly outweigh the memory used for
3357 * metadata. It also keeps this calculation nice and simple.
3358 *
3359 * RETURNS:
3360 * Total number of populated backing pages in use by the allocator.
3361 */
3362 unsigned long pcpu_nr_pages(void)
3363 {
3364 return data_race(READ_ONCE(pcpu_nr_populated)) * pcpu_nr_units;
3365 }
3366
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Powered by blists - more mailing lists