All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android15-6.6-2025-05 0/2] mm/page_alloc.c:327:15: sparse: sparse: symbol 'nr_free_highatomic' was not declared. Should it be static?
Date: Wed, 01 Apr 2026 10:14:27 +0800	[thread overview]
Message-ID: <202604011007.llcDN5Su-lkp@intel.com> (raw)

Hi Kalesh,

First bad commit (maybe != root cause):

tree:   https://android.googlesource.com/kernel/common android15-6.6-2025-05
head:   b3fc1858b36caef7f14dd6d6ec611eba4d5eee85
commit: 7b1f522c80c811c59e056b899b26c684780442fd [0/2] ANDROID: GKI: deferred split queue corruption - ABI fixup
config: x86_64-randconfig-122-20260401 (https://download.01.org/0day-ci/archive/20260401/202604011007.llcDN5Su-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260401/202604011007.llcDN5Su-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/202604011007.llcDN5Su-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
   mm/page_alloc.c:195:1: sparse: sparse: symbol 'restrict_cma_redirect' was not declared. Should it be static?
   mm/page_alloc.c:1384:25: sparse: sparse: incorrect type in argument 3 (different base types) @@     expected restricted int flags @@     got restricted fpi_t [usertype] fpi_flags @@
   mm/page_alloc.c:1384:25: sparse:     expected restricted int flags
   mm/page_alloc.c:1384:25: sparse:     got restricted fpi_t [usertype] fpi_flags
   mm/page_alloc.c:1392:25: sparse: sparse: incorrect type in argument 3 (different base types) @@     expected restricted int flags @@     got restricted fpi_t [usertype] fpi_flags @@
   mm/page_alloc.c:1392:25: sparse:     expected restricted int flags
   mm/page_alloc.c:1392:25: sparse:     got restricted fpi_t [usertype] fpi_flags
>> mm/page_alloc.c:327:15: sparse: sparse: symbol 'nr_free_highatomic' was not declared. Should it be static?
   mm/page_alloc.c:915:31: sparse: sparse: cast from restricted fpi_t
   mm/page_alloc.c:915:31: sparse: sparse: cast from restricted fpi_t
   mm/page_alloc.c:915:31: sparse: sparse: cast from restricted fpi_t
   mm/page_alloc.c:2738:6: sparse: sparse: context imbalance in 'free_unref_page' - different lock contexts for basic block
   mm/page_alloc.c:2835:33: sparse: sparse: context imbalance in 'free_unref_folios' - unexpected unlock
   mm/page_alloc.c:915:31: sparse: sparse: cast from restricted fpi_t
   mm/page_alloc.c:3137:20: sparse: sparse: context imbalance in 'rmqueue_pcplist' - different lock contexts for basic block
   mm/page_alloc.c:4890:9: sparse: sparse: context imbalance in '__alloc_pages_bulk' - different lock contexts for basic block

vim +/nr_free_highatomic +327 mm/page_alloc.c

60f30350fd69a3 Vlastimil Babka 2016-03-15  326  
d5ace9d4dd020b Kalesh Singh    2025-05-28 @327  unsigned long nr_free_highatomic[MAX_NR_ZONES] = {0};
d5ace9d4dd020b Kalesh Singh    2025-05-28  328  

:::::: The code at line 327 was first introduced by commit
:::::: d5ace9d4dd020b31be684cfd095e876fe59ae65f ANDROID: GKI: page_alloc ABI fixup

:::::: TO: Kalesh Singh <kaleshsingh@google.com>
:::::: CC: Kalesh Singh <kaleshsingh@google.com>

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

                 reply	other threads:[~2026-04-01  2:15 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=202604011007.llcDN5Su-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=cros-kernel-buildreports@googlegroups.com \
    --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.