From: kernel test robot <lkp@intel.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [linux-next:master 12115/12616] mm/page_alloc.c:6244:9: error: too many arguments to function 'cpu_vm_stats_fold'
Date: Wed, 19 Apr 2023 04:55:24 +0800 [thread overview]
Message-ID: <202304190402.keC5huSY-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 4aa1da8d99724f6c0b762b58a71cee7c5e2e109b
commit: 938b4fea29fd04e2e7dc7fbb15bacedeafaa765d [12115/12616] vmstat: add pcp remote node draining via cpu_vm_stats_fold
config: i386-randconfig-a016-20211118 (https://download.01.org/0day-ci/archive/20230419/202304190402.keC5huSY-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-8) 11.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=938b4fea29fd04e2e7dc7fbb15bacedeafaa765d
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout 938b4fea29fd04e2e7dc7fbb15bacedeafaa765d
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=i386 olddefconfig
make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202304190402.keC5huSY-lkp@intel.com/
Note: the linux-next/master HEAD 4aa1da8d99724f6c0b762b58a71cee7c5e2e109b builds fine.
It may have been fixed somewhere.
All errors (new ones prefixed by >>):
mm/page_alloc.c: In function 'page_alloc_cpu_dead':
>> mm/page_alloc.c:6244:9: error: too many arguments to function 'cpu_vm_stats_fold'
6244 | cpu_vm_stats_fold(cpu, false);
| ^~~~~~~~~~~~~~~~~
In file included from include/linux/mm.h:2116,
from mm/page_alloc.c:19:
include/linux/vmstat.h:411:20: note: declared here
411 | static inline void cpu_vm_stats_fold(int cpu) { }
| ^~~~~~~~~~~~~~~~~
vim +/cpu_vm_stats_fold +6244 mm/page_alloc.c
6223
6224 static int page_alloc_cpu_dead(unsigned int cpu)
6225 {
6226 struct zone *zone;
6227
6228 lru_add_drain_cpu(cpu);
6229 mlock_drain_remote(cpu);
6230 drain_pages(cpu);
6231
6232 /*
6233 * Spill the event counters of the dead processor
6234 * into the current processors event counters.
6235 * This artificially elevates the count of the current
6236 * processor.
6237 */
6238 vm_events_fold_cpu(cpu);
6239
6240 /*
6241 * Zero the differential counters of the dead processor
6242 * so that the vm statistics are consistent.
6243 */
> 6244 cpu_vm_stats_fold(cpu, false);
6245
6246 for_each_populated_zone(zone)
6247 zone_pcp_update(zone, 0);
6248
6249 return 0;
6250 }
6251
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
next reply other threads:[~2023-04-18 20:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 20:55 kernel test robot [this message]
2023-04-18 21:05 ` Andrew Morton
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=202304190402.keC5huSY-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=mtosatti@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox