All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC PATCH 1/1] mm: vmscan: keep anon scanning enabled when swapcache folios are present
Date: Sat, 2 May 2026 09:21:17 +0800	[thread overview]
Message-ID: <202605020936.BWbySFnE-lkp@intel.com> (raw)
In-Reply-To: <20260427103532.5623-2-thomas.hellstrom@linux.intel.com>

Hi Thomas,

[This is a private test report for your RFC patch.]
kernel test robot noticed the following build errors:

[auto build test ERROR on akpm-mm/mm-everything]
[also build test ERROR on linus/master v7.1-rc1 next-20260430]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Thomas-Hellstr-m/mm-vmscan-keep-anon-scanning-enabled-when-swapcache-folios-are-present/20260428-183540
base:   https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
patch link:    https://lore.kernel.org/r/20260427103532.5623-2-thomas.hellstrom%40linux.intel.com
patch subject: [RFC PATCH 1/1] mm: vmscan: keep anon scanning enabled when swapcache folios are present
config: m68k-allnoconfig (https://download.01.org/0day-ci/archive/20260502/202605020936.BWbySFnE-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 15.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260502/202605020936.BWbySFnE-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/202605020936.BWbySFnE-lkp@intel.com/

All errors (new ones prefixed by >>):

   In file included from include/linux/mm.h:2937,
                    from mm/vmscan.c:15:
   mm/vmscan.c: In function 'can_reclaim_anon_pages':
>> mm/vmscan.c:365:45: error: 'NR_SWAPCACHE' undeclared (first use in this function)
     365 |         if (node_page_state(NODE_DATA(nid), NR_SWAPCACHE) > 0)
         |                                             ^~~~~~~~~~~~
   include/linux/vmstat.h:265:60: note: in definition of macro 'node_page_state'
     265 | #define node_page_state(node, item) global_node_page_state(item)
         |                                                            ^~~~
   mm/vmscan.c:365:45: note: each undeclared identifier is reported only once for each function it appears in
     365 |         if (node_page_state(NODE_DATA(nid), NR_SWAPCACHE) > 0)
         |                                             ^~~~~~~~~~~~
   include/linux/vmstat.h:265:60: note: in definition of macro 'node_page_state'
     265 | #define node_page_state(node, item) global_node_page_state(item)
         |                                                            ^~~~


vim +/NR_SWAPCACHE +365 mm/vmscan.c

   341	
   342	static inline bool can_reclaim_anon_pages(struct mem_cgroup *memcg,
   343						  int nid,
   344						  struct scan_control *sc)
   345	{
   346		if (memcg == NULL) {
   347			/*
   348			 * For non-memcg reclaim, is there
   349			 * space in any swap device?
   350			 */
   351			if (get_nr_swap_pages() > 0)
   352				return true;
   353		} else {
   354			/* Is the memcg below its swap limit? */
   355			if (mem_cgroup_get_nr_swap_pages(memcg) > 0)
   356				return true;
   357		}
   358	
   359		/*
   360		 * Even with no free swap slots, anon folios already in the swap cache
   361		 * carry a pre-allocated slot and can be written back and freed from RAM
   362		 * without consuming a new one.  Do not suppress anon scanning when such
   363		 * folios are present on this node.
   364		 */
 > 365		if (node_page_state(NODE_DATA(nid), NR_SWAPCACHE) > 0)
   366			return true;
   367	
   368		/*
   369		 * The page can not be swapped.
   370		 *
   371		 * Can it be reclaimed from this node via demotion?
   372		 */
   373		return can_demote(nid, sc, memcg);
   374	}
   375	

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

  reply	other threads:[~2026-05-02  1:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-27 10:35 [RFC PATCH 0/1] Fix halted scanning of swap-cache folios Thomas Hellström
2026-04-27 10:35 ` [RFC PATCH 1/1] mm: vmscan: keep anon scanning enabled when swapcache folios are present Thomas Hellström
2026-05-02  1:21   ` kernel test robot [this message]
2026-05-02  2:46   ` kernel test robot
2026-04-27 13:36 ` ✗ CI.checkpatch: warning for Fix halted scanning of swap-cache folios Patchwork
2026-04-27 13:37 ` ✓ CI.KUnit: success " Patchwork
2026-04-27 14:55 ` ✓ Xe.CI.BAT: " Patchwork
2026-04-27 16:45 ` ✗ Xe.CI.FULL: failure " Patchwork

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=202605020936.BWbySFnE-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=thomas.hellstrom@linux.intel.com \
    /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.