From: kernel test robot <lkp@intel.com>
To: Yueyang Pan <pyyjason@gmail.com>,
Suren Baghdasaryan <surenb@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Vlastimil Babka <vbabka@suse.cz>, Michal Hocko <mhocko@suse.com>,
Brendan Jackman <jackmanb@google.com>,
Johannes Weiner <hannes@cmpxchg.org>, Zi Yan <ziy@nvidia.com>,
Vishal Moola <vishal.moola@gmail.com>,
Shakeel Butt <shakeel.butt@linux.dev>,
Usama Arif <usamaarif642@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
kernel-team@meta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] mm/show_mem: Add trylock while printing alloc info
Date: Wed, 3 Sep 2025 17:47:35 +0800 [thread overview]
Message-ID: <202509031744.HcibSETe-lkp@intel.com> (raw)
In-Reply-To: <1491df0ac12a7626b7c9b00e26a6e10adb8c9045.1756827906.git.pyyjason@gmail.com>
Hi Yueyang,
kernel test robot noticed the following build warnings:
[auto build test WARNING on akpm-mm/mm-everything]
url: https://github.com/intel-lab-lkp/linux/commits/Yueyang-Pan/mm-show_mem-Dump-the-status-of-the-mem-alloc-profiling-before-printing/20250903-000616
base: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
patch link: https://lore.kernel.org/r/1491df0ac12a7626b7c9b00e26a6e10adb8c9045.1756827906.git.pyyjason%40gmail.com
patch subject: [PATCH v2 2/2] mm/show_mem: Add trylock while printing alloc info
config: i386-buildonly-randconfig-001-20250903 (https://download.01.org/0day-ci/archive/20250903/202509031744.HcibSETe-lkp@intel.com/config)
compiler: gcc-13 (Debian 13.3.0-16) 13.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250903/202509031744.HcibSETe-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/202509031744.HcibSETe-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from mm/show_mem.c:18:
mm/show_mem.c: In function 'show_free_areas':
mm/show_mem.c:336:49: error: 'NR_ZSPAGES' undeclared (first use in this function); did you mean 'NR_STATS'?
336 | K(zone_page_state(zone, NR_ZSPAGES)),
| ^~~~~~~~~~
mm/internal.h:560:16: note: in definition of macro 'K'
560 | #define K(x) ((x) << (PAGE_SHIFT-10))
| ^
include/linux/printk.h:512:26: note: in expansion of macro 'printk_index_wrap'
512 | #define printk(fmt, ...) printk_index_wrap(_printk, fmt, ##__VA_ARGS__)
| ^~~~~~~~~~~~~~~~~
mm/show_mem.c:298:17: note: in expansion of macro 'printk'
298 | printk(KERN_CONT
| ^~~~~~
mm/show_mem.c:336:49: note: each undeclared identifier is reported only once for each function it appears in
336 | K(zone_page_state(zone, NR_ZSPAGES)),
| ^~~~~~~~~~
mm/internal.h:560:16: note: in definition of macro 'K'
560 | #define K(x) ((x) << (PAGE_SHIFT-10))
| ^
include/linux/printk.h:512:26: note: in expansion of macro 'printk_index_wrap'
512 | #define printk(fmt, ...) printk_index_wrap(_printk, fmt, ##__VA_ARGS__)
| ^~~~~~~~~~~~~~~~~
mm/show_mem.c:298:17: note: in expansion of macro 'printk'
298 | printk(KERN_CONT
| ^~~~~~
In file included from include/linux/spinlock.h:89,
from include/linux/wait.h:9,
from include/linux/wait_bit.h:8,
from include/linux/fs.h:7,
from include/linux/highmem.h:5,
from include/linux/bvec.h:10,
from include/linux/blk_types.h:10,
from include/linux/blkdev.h:9,
from mm/show_mem.c:8:
mm/show_mem.c: In function '__show_mem':
>> mm/show_mem.c:399:32: warning: unused variable 'mem_alloc_profiling_spinlock' [-Wunused-variable]
399 | static DEFINE_SPINLOCK(mem_alloc_profiling_spinlock);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
include/linux/spinlock_types.h:43:44: note: in definition of macro 'DEFINE_SPINLOCK'
43 | #define DEFINE_SPINLOCK(x) spinlock_t x = __SPIN_LOCK_UNLOCKED(x)
| ^
vim +/mem_alloc_profiling_spinlock +399 mm/show_mem.c
396
397 void __show_mem(unsigned int filter, nodemask_t *nodemask, int max_zone_idx)
398 {
> 399 static DEFINE_SPINLOCK(mem_alloc_profiling_spinlock);
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-09-03 9:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 15:57 [PATCH v2 0/2] mm/show_mem: Bug fix for print mem alloc info Yueyang Pan
2025-09-02 15:57 ` [PATCH v2 1/2] mm/show_mem: Dump the status of the mem alloc profiling before printing Yueyang Pan
2025-09-03 9:26 ` Vlastimil Babka
2025-09-03 9:34 ` Yueyang Pan
2025-09-03 10:12 ` Vlastimil Babka
2025-09-03 10:12 ` Usama Arif
2025-09-02 15:57 ` [PATCH v2 2/2] mm/show_mem: Add trylock while printing alloc info Yueyang Pan
2025-09-03 9:22 ` Vlastimil Babka
2025-09-03 9:31 ` Usama Arif
2025-09-03 9:47 ` kernel test robot [this message]
2025-09-03 10:16 ` Vlastimil Babka
2025-09-03 10:24 ` Yueyang Pan
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=202509031744.HcibSETe-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=jackmanb@google.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pyyjason@gmail.com \
--cc=shakeel.butt@linux.dev \
--cc=surenb@google.com \
--cc=usamaarif642@gmail.com \
--cc=vbabka@suse.cz \
--cc=vishal.moola@gmail.com \
--cc=ziy@nvidia.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;
as well as URLs for NNTP newsgroup(s).