From: kernel test robot <lkp@intel.com>
To: Yosry Ahmed <yosryahmed@google.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [linux-next:master 3583/3746] mm/memcontrol.c:6817:25: error: implicit declaration of function 'mem_cgroup_kmem_record'; did you mean 'mem_cgroup_id_remove'?
Date: Thu, 3 Feb 2022 04:37:48 +0800 [thread overview]
Message-ID: <202202030427.iuiyx1zZ-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 6abab1b81b657ca74b7c443e832d95c87901e75b
commit: 3f0d9563b9f925e35b72b2e2abfe36bf28fc3549 [3583/3746] memcg: add per-memcg total kernel memory stat
config: parisc-randconfig-r006-20220201 (https://download.01.org/0day-ci/archive/20220203/202202030427.iuiyx1zZ-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=3f0d9563b9f925e35b72b2e2abfe36bf28fc3549
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 3f0d9563b9f925e35b72b2e2abfe36bf28fc3549
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=parisc SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
mm/memcontrol.c: In function 'uncharge_batch':
>> mm/memcontrol.c:6817:25: error: implicit declaration of function 'mem_cgroup_kmem_record'; did you mean 'mem_cgroup_id_remove'? [-Werror=implicit-function-declaration]
6817 | mem_cgroup_kmem_record(ug->memcg, -ug->nr_kmem);
| ^~~~~~~~~~~~~~~~~~~~~~
| mem_cgroup_id_remove
cc1: some warnings being treated as errors
vim +6817 mm/memcontrol.c
6807
6808 static void uncharge_batch(const struct uncharge_gather *ug)
6809 {
6810 unsigned long flags;
6811
6812 if (ug->nr_memory) {
6813 page_counter_uncharge(&ug->memcg->memory, ug->nr_memory);
6814 if (do_memsw_account())
6815 page_counter_uncharge(&ug->memcg->memsw, ug->nr_memory);
6816 if (ug->nr_kmem)
> 6817 mem_cgroup_kmem_record(ug->memcg, -ug->nr_kmem);
6818 memcg_oom_recover(ug->memcg);
6819 }
6820
6821 local_irq_save(flags);
6822 __count_memcg_events(ug->memcg, PGPGOUT, ug->pgpgout);
6823 __this_cpu_add(ug->memcg->vmstats_percpu->nr_page_events, ug->nr_memory);
6824 memcg_check_events(ug->memcg, ug->nid);
6825 local_irq_restore(flags);
6826
6827 /* drop reference from uncharge_folio */
6828 css_put(&ug->memcg->css);
6829 }
6830
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2022-02-02 20:38 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=202202030427.iuiyx1zZ-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=yosryahmed@google.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