linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: zhongjinji@honor.com, linux-mm@kvack.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	akpm@linux-foundation.org, yuzhao@google.com,
	linux-kernel@vger.kernel.org, yipengxiang@honor.com,
	liulu.liu@honor.com, feng.han@honor.com
Subject: Re: [PATCH] mm: vmscan: Page scanning depends on swappiness and refault
Date: Sat, 28 Jun 2025 15:32:08 +0800	[thread overview]
Message-ID: <202506281519.wHSXE6l0-lkp@intel.com> (raw)
In-Reply-To: <20250627162606.30609-1-zhongjinji@honor.com>

Hi,

kernel test robot noticed the following build errors:

[auto build test ERROR on linus/master]
[also build test ERROR on v6.16-rc3]
[cannot apply to akpm-mm/mm-everything next-20250627]
[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/zhongjinji-honor-com/mm-vmscan-Page-scanning-depends-on-swappiness-and-refault/20250628-002820
base:   linus/master
patch link:    https://lore.kernel.org/r/20250627162606.30609-1-zhongjinji%40honor.com
patch subject: [PATCH] mm: vmscan: Page scanning depends on swappiness and refault
config: x86_64-buildonly-randconfig-005-20250628 (https://download.01.org/0day-ci/archive/20250628/202506281519.wHSXE6l0-lkp@intel.com/config)
compiler: clang version 20.1.7 (https://github.com/llvm/llvm-project 6146a88f60492b520a36f8f8f3231e15f3cc6082)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250628/202506281519.wHSXE6l0-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/202506281519.wHSXE6l0-lkp@intel.com/

All errors (new ones prefixed by >>):

>> mm/vmscan.c:2783:24: error: use of undeclared identifier 'swappiness'
    2783 |         if ((!sc->priority && swappiness) || sc->file_is_tiny)
         |                               ^
>> mm/vmscan.c:4100:33: error: expected identifier
    4100 |         if (seq <= READ_ONCE(mm_state->.seq))
         |                                        ^
>> mm/vmscan.c:4100:33: error: expected identifier
>> mm/vmscan.c:4100:33: error: expected identifier
>> mm/vmscan.c:4100:33: error: expected identifier
>> mm/vmscan.c:4100:33: error: expected identifier
>> mm/vmscan.c:4100:33: error: expected identifier
>> mm/vmscan.c:4100:33: error: expected identifier
>> mm/vmscan.c:4154:3: error: call to undeclared function 'for_each_age_able_type'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
    4154 |                 for_each_age_able_type(type, can_age) {
         |                 ^
>> mm/vmscan.c:4154:40: error: expected ';' after expression
    4154 |                 for_each_age_able_type(type, can_age) {
         |                                                      ^
         |                                                      ;
   10 errors generated.


vim +/swappiness +2783 mm/vmscan.c

  2770	
  2771	static int get_swappiness(struct lruvec *lruvec, struct scan_control *sc)
  2772	{
  2773		struct mem_cgroup *memcg = lruvec_memcg(lruvec);
  2774		struct pglist_data *pgdat = lruvec_pgdat(lruvec);
  2775	
  2776		if (!sc->may_swap)
  2777			return 0;
  2778	
  2779		if (!can_demote(pgdat->node_id, sc, memcg) &&
  2780		    mem_cgroup_get_nr_swap_pages(memcg) < MIN_LRU_BATCH)
  2781			return 0;
  2782	
> 2783		if ((!sc->priority && swappiness) || sc->file_is_tiny)
  2784			return BALACNCE_SWAPPINESS;
  2785	
  2786		return sc_swappiness(sc, memcg);
  2787	}
  2788	

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


  parent reply	other threads:[~2025-06-28  7:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-27 16:26 zhongjinji
2025-06-27 21:09 ` Andrew Morton
2025-06-28  7:32 ` kernel test robot [this message]
2025-06-28  7:52 ` kernel test robot
  -- strict thread matches above, loose matches on Subject: below --
2025-06-27 15:55 zhongjinji
2025-06-28  7:08 ` Sabyrzhan Tasbolatov

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=202506281519.wHSXE6l0-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=feng.han@honor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=liulu.liu@honor.com \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=yipengxiang@honor.com \
    --cc=yuzhao@google.com \
    --cc=zhongjinji@honor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox