All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Gregory Price <gourry@gourry.net>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [gourryinverse:scratch/gourry/managed_nodes/rfc6-complete 8/67] mm/page_alloc.c:7386:17: error: implicit declaration of function 'folio_test_clear_young'; did you mean 'folio_test_clear_lru'?
Date: Tue, 15 Sep 2026 08:21:21 +0200	[thread overview]
Message-ID: <202609150733.bokShgrT-lkp@intel.com> (raw)

tree:   https://github.com/gourryinverse/linux scratch/gourry/managed_nodes/rfc6-complete
head:   0423df59f3f085592c3ff59834eeae067ee75158
commit: 4af770f6b4623768abd534b154c6d8136f601cac [8/67] mm/page_alloc: let alloc_contig_range() try harder
config: i386-randconfig-054-20260915 (https://download.01.org/0day-ci/archive/20260915/202609150733.bokShgrT-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/20260915/202609150733.bokShgrT-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/202609150733.bokShgrT-lkp@intel.com/

All errors (new ones prefixed by >>):

   mm/page_alloc.c: In function 'contig_range_reclaim':
>> mm/page_alloc.c:7386:17: error: implicit declaration of function 'folio_test_clear_young'; did you mean 'folio_test_clear_lru'? [-Wimplicit-function-declaration]
    7386 |                 folio_test_clear_young(folio);
         |                 ^~~~~~~~~~~~~~~~~~~~~~
         |                 folio_test_clear_lru


vim +7386 mm/page_alloc.c

  7363	
  7364	/*
  7365	 * ACR_FLAGS_RECLAIM: evict the folios in [@start, @end) that migration could
  7366	 * not move.  Ages them down first so reclaim does not decline on the strength
  7367	 * of a recent reference -- the caller is not asking for a hint.
  7368	 *
  7369	 * Return: pages reclaimed.
  7370	 */
  7371	static unsigned long contig_range_reclaim(unsigned long start, unsigned long end)
  7372	{
  7373		unsigned long pfn = start, reclaimed = 0, isolated = 0;
  7374		LIST_HEAD(folio_list);
  7375	
  7376		while (pfn < end) {
  7377			struct folio *folio = contig_get_lru_folio(pfn);
  7378	
  7379			if (!folio) {
  7380				pfn++;
  7381				continue;
  7382			}
  7383			pfn += folio_nr_pages(folio);
  7384	
  7385			folio_clear_referenced(folio);
> 7386			folio_test_clear_young(folio);
  7387			if (!folio_isolate_lru(folio))
  7388				goto put;
  7389			if (folio_test_unevictable(folio)) {
  7390				folio_putback_lru(folio);
  7391			} else {
  7392				list_add(&folio->lru, &folio_list);
  7393				isolated += folio_nr_pages(folio);
  7394			}
  7395	put:
  7396			/* isolation took its own reference; drop the lookup's */
  7397			folio_put(folio);
  7398	
  7399			if (isolated >= CONTIG_RECLAIM_BATCH) {
  7400				reclaimed += reclaim_pages(&folio_list);
  7401				isolated = 0;
  7402				cond_resched();
  7403				if (fatal_signal_pending(current))
  7404					break;
  7405			}
  7406		}
  7407		reclaimed += reclaim_pages(&folio_list);
  7408	
  7409		return reclaimed;
  7410	}
  7411	

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

                 reply	other threads:[~2026-09-15  6:21 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=202609150733.bokShgrT-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=gourry@gourry.net \
    --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.