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/1] mm/vmscan.c:4372:6: warning: no previous prototype for 'isolate_folio'
Date: Mon, 22 Jun 2026 18:38:55 +0800 [thread overview]
Message-ID: <202606221823.Qfd5T6WA-lkp@intel.com> (raw)
Hi yipeng,
FYI, the error/warning still remains.
tree: https://android.googlesource.com/kernel/common android16-6.12
head: 74c43557c8aed4002d058c4e88c768a6086df9c2
commit: 0e47a7391b3e2e57c4769f14a7be0ba7b56b10ca [0/1] ANDROID: mm: export isolate_folio and reclaim_pages
config: x86_64-randconfig-071-20260622 (https://download.01.org/0day-ci/archive/20260622/202606221823.Qfd5T6WA-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/20260622/202606221823.Qfd5T6WA-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/202606221823.Qfd5T6WA-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> mm/vmscan.c:4372:6: warning: no previous prototype for 'isolate_folio' [-Wmissing-prototypes]
4372 | bool isolate_folio(struct lruvec *lruvec, struct folio *folio, struct scan_control *sc)
| ^~~~~~~~~~~~~
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for CAN_RX_OFFLOAD
Depends on [n]: NETDEVICES [=y] && CAN_DEV [=n] && CAN_NETLINK [=n]
Selected by [y]:
- GKI_HIDDEN_MCP251XFD_CONFIGS [=y] && 64BIT [=y]
vim +/isolate_folio +4372 mm/vmscan.c
4371
> 4372 bool isolate_folio(struct lruvec *lruvec, struct folio *folio, struct scan_control *sc)
4373 {
4374 bool success;
4375
4376 /* swap constrained */
4377 if (!(sc->gfp_mask & __GFP_IO) &&
4378 (folio_test_dirty(folio) ||
4379 (folio_test_anon(folio) && !folio_test_swapcache(folio))))
4380 return false;
4381
4382 /* raced with release_pages() */
4383 if (!folio_try_get(folio))
4384 return false;
4385
4386 /* raced with another isolation */
4387 if (!folio_test_clear_lru(folio)) {
4388 folio_put(folio);
4389 return false;
4390 }
4391
4392 /* see the comment on MAX_NR_TIERS */
4393 if (!folio_test_referenced(folio))
4394 set_mask_bits(&folio->flags, LRU_REFS_MASK | LRU_REFS_FLAGS, 0);
4395
4396 /* for shrink_folio_list() */
4397 folio_clear_reclaim(folio);
4398 folio_clear_referenced(folio);
4399
4400 success = lru_gen_del_folio(lruvec, folio, true);
4401 VM_WARN_ON_ONCE_FOLIO(!success, folio);
4402
4403 return true;
4404 }
4405 EXPORT_SYMBOL_GPL(isolate_folio);
4406
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-06-22 10:39 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=202606221823.Qfd5T6WA-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.