All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [android-common:android17-6.18 1/1] mm/memory.c:96:2: sparse: sparse: Unfortunate NUMA and NUMA Balancing config, growing page-frame for last_cpupid.
Date: Fri, 06 Nov 2026 08:40:59 +0100	[thread overview]
Message-ID: <202611060800.G6eVPKsw-lkp@intel.com> (raw)

:::::: 
:::::: Manual check reason: "low confidence static check first_new_problem: mm/memory.c:96:2: sparse: sparse: Unfortunate NUMA and NUMA Balancing config, growing page-frame for last_cpupid."
:::::: 

BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: cros-kernel-buildreports@googlegroups.com

tree:   https://android.googlesource.com/kernel/common android17-6.18
head:   b835509d43ba8175031f800f12347f8e8206a471
commit: 9d29ba85d8a2c505b2d049568c3b1d29c4e0c2fd [1/1] ANDROID: mm: mglru: let MADV_WILLNEED pages take extra trip in active list
:::::: branch date: 12 hours ago
:::::: commit date: 4 weeks ago
config: x86_64-randconfig-r2300-20261106 (https://download.01.org/0day-ci/archive/20261106/202611060800.G6eVPKsw-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
sparse: v0.6.5-rc1-21-g84ec0658
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261106/202611060800.G6eVPKsw-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/r/202611060800.G6eVPKsw-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> mm/memory.c:96:2: sparse: sparse: Unfortunate NUMA and NUMA Balancing config, growing page-frame for last_cpupid.
   mm/memory.c:167:15: sparse: sparse: symbol 'zero_pfn' was not declared. Should it be static?
   mm/memory.c:300:9: sparse: sparse: incompatible types in conditional expression (different base types):
   mm/memory.c:300:9: sparse:    void
   mm/memory.c:300:9: sparse:    int

vim +96 mm/memory.c

42b7772812d15b8 Jan Beulich    2008-07-23  94  
af27d9403f5b806 Arnd Bergmann  2018-02-16  95  #if defined(LAST_CPUPID_NOT_IN_PAGE_FLAGS) && !defined(CONFIG_COMPILE_TEST)
90572890d202527 Peter Zijlstra 2013-10-07 @96  #warning Unfortunate NUMA and NUMA Balancing config, growing page-frame for last_cpupid.
75980e97daccfc6 Peter Zijlstra 2013-02-22  97  #endif
75980e97daccfc6 Peter Zijlstra 2013-02-22  98  

:::::: The code at line 96 was first introduced by commit
:::::: 90572890d202527c366aa9489b32404e88a7c020 mm: numa: Change page last {nid,pid} into {cpu,pid}

:::::: TO: Peter Zijlstra <peterz@infradead.org>
:::::: CC: Ingo Molnar <mingo@kernel.org>

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2026-11-06  7:41 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=202611060800.G6eVPKsw-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=oe-kbuild@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.