All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: aubrey.li@linux.intel.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [anolis-intel-cloud:devel-6.6 1019/1019] mm/memcontrol.c:8380:9: error: implicit declaration of function 'mem_cgroup_attach_unevictable'
Date: Tue, 08 Sep 2026 16:15:03 +0200	[thread overview]
Message-ID: <202609081655.HELc1BBu-lkp@intel.com> (raw)

tree:   https://gitee.com/anolis/intel-cloud-kernel.git devel-6.6
head:   b4ec01ca5aac08347802786e2513d22bcc37d843
commit: 9f95c5d2e9cad8cbf1712aadceb8268703e0eff7 [1019/1019] anolis: mm/unevictable: move cgroup migration arm/disarm from can_attach to attach
config: x86_64-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20260908/202609081655.HELc1BBu-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/20260908/202609081655.HELc1BBu-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/202609081655.HELc1BBu-lkp@intel.com/

All errors (new ones prefixed by >>):

   mm/memcontrol.c: In function 'mem_cgroup_attach':
>> mm/memcontrol.c:8380:9: error: implicit declaration of function 'mem_cgroup_attach_unevictable' [-Wimplicit-function-declaration]
    8380 |         mem_cgroup_attach_unevictable(tset);
         |         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   mm/memcontrol.c: In function 'mem_cgroup_fork':
   mm/memcontrol.c:8386:9: error: implicit declaration of function 'unevict_task_fork'; did you mean 'exit_task_work'? [-Wimplicit-function-declaration]
    8386 |         unevict_task_fork(task);
         |         ^~~~~~~~~~~~~~~~~
         |         exit_task_work


vim +/mem_cgroup_attach_unevictable +8380 mm/memcontrol.c

  8356	
  8357	#ifdef CONFIG_LRU_GEN
  8358	static void mem_cgroup_attach(struct cgroup_taskset *tset)
  8359	{
  8360		struct task_struct *task;
  8361		struct cgroup_subsys_state *css;
  8362	
  8363		/* find the first leader if there is any */
  8364		cgroup_taskset_for_each_leader(task, css, tset)
  8365			break;
  8366	
  8367		if (!task)
  8368			return;
  8369	
  8370		task_lock(task);
  8371		if (task->mm && READ_ONCE(task->mm->owner) == task)
  8372			lru_gen_migrate_mm(task->mm);
  8373		task_unlock(task);
  8374	
  8375		mem_cgroup_attach_unevictable(tset);
  8376	}
  8377	#else
  8378	static void mem_cgroup_attach(struct cgroup_taskset *tset)
  8379	{
> 8380		mem_cgroup_attach_unevictable(tset);
  8381	}
  8382	#endif /* CONFIG_LRU_GEN */
  8383	

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

                 reply	other threads:[~2026-09-08 14:15 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=202609081655.HELc1BBu-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=aubrey.li@linux.intel.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 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.