From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android16-6.12 0/2] mm/vmscan.c:5285:59: error: 'root_mem_cgroup' undeclared; did you mean 'parent_mem_cgroup'?
Date: Thu, 08 Oct 2026 09:54:00 +0200 [thread overview]
Message-ID: <202610080912.dCrKVMaZ-lkp@intel.com> (raw)
tree: https://android.googlesource.com/kernel/common android16-6.12
head: c7ad8c94d6193bff72b385b1cf3fb753de09f780
commit: aa438a63587f2d9dc1888265365ff3de338ba16f [0/2] ANDROID: mm: mglru: invoke root shrinker before memcg-specific ones
config: x86_64-randconfig-2101-20261008 (https://download.01.org/0day-ci/archive/20261008/202610080912.dCrKVMaZ-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261008/202610080912.dCrKVMaZ-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/202610080912.dCrKVMaZ-lkp@intel.com/
All errors (new ones prefixed by >>):
mm/vmscan.c:4695:6: warning: no previous prototype for 'isolate_folio' [-Wmissing-prototypes]
4695 | bool isolate_folio(struct lruvec *lruvec, struct folio *folio, struct scan_control *sc)
| ^~~~~~~~~~~~~
mm/vmscan.c: In function 'lru_gen_shrink_node':
>> mm/vmscan.c:5285:59: error: 'root_mem_cgroup' undeclared (first use in this function); did you mean 'parent_mem_cgroup'?
5285 | shrink_slab(sc->gfp_mask, pgdat->node_id, root_mem_cgroup,
| ^~~~~~~~~~~~~~~
| parent_mem_cgroup
mm/vmscan.c:5285:59: note: each undeclared identifier is reported only once for each function it appears in
vim +5285 mm/vmscan.c
5255
5256 static void lru_gen_shrink_node(struct pglist_data *pgdat, struct scan_control *sc)
5257 {
5258 struct blk_plug plug;
5259 unsigned long reclaimed = sc->nr_reclaimed;
5260
5261 VM_WARN_ON_ONCE(!root_reclaim(sc));
5262
5263 /*
5264 * Unmapped clean folios are already prioritized. Scanning for more of
5265 * them is likely futile and can cause high reclaim latency when there
5266 * is a large number of memcgs.
5267 */
5268 if (!sc->may_writepage || !sc->may_unmap)
5269 goto done;
5270
5271 lru_add_drain();
5272
5273 blk_start_plug(&plug);
5274
5275 set_mm_walk(pgdat, sc->proactive);
5276
5277 set_initial_priority(pgdat, sc);
5278
5279 if (current_is_kswapd())
5280 sc->nr_reclaimed = 0;
5281
5282 if (mem_cgroup_disabled()) {
5283 shrink_one(&pgdat->__lruvec, sc);
5284 } else {
> 5285 shrink_slab(sc->gfp_mask, pgdat->node_id, root_mem_cgroup,
5286 sc->priority);
5287 if (sc->nr_reclaimed < sc->nr_to_reclaim)
5288 shrink_many(pgdat, sc);
5289 }
5290 if (current_is_kswapd())
5291 sc->nr_reclaimed += reclaimed;
5292
5293 clear_mm_walk();
5294
5295 blk_finish_plug(&plug);
5296 done:
5297 if (sc->nr_reclaimed > reclaimed)
5298 pgdat->kswapd_failures = 0;
5299 }
5300
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-10-08 7:55 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=202610080912.dCrKVMaZ-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.