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:8390:9: error: implicit declaration of function 'unevict_task_fork'; did you mean 'exit_task_work'?
Date: Tue, 08 Sep 2026 13:11:40 +0200 [thread overview]
Message-ID: <202609081337.J1ul7JmK-lkp@intel.com> (raw)
tree: https://gitee.com/anolis/intel-cloud-kernel.git devel-6.6
head: b4ec01ca5aac08347802786e2513d22bcc37d843
commit: d30f7906f08ec3a4b9d04521557c5cf4dcea6d7a [1019/1019] anolis: mm/unevictable: arm forked children via memcg fork hook
config: x86_64-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20260908/202609081337.J1ul7JmK-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/202609081337.J1ul7JmK-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/202609081337.J1ul7JmK-lkp@intel.com/
All errors (new ones prefixed by >>):
mm/memcontrol.c: In function 'mem_cgroup_fork':
>> mm/memcontrol.c:8390:9: error: implicit declaration of function 'unevict_task_fork'; did you mean 'exit_task_work'? [-Wimplicit-function-declaration]
8390 | unevict_task_fork(task);
| ^~~~~~~~~~~~~~~~~
| exit_task_work
vim +8390 mm/memcontrol.c
8387
8388 static void mem_cgroup_fork(struct task_struct *task)
8389 {
> 8390 unevict_task_fork(task);
8391 }
8392
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-09-08 11:12 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=202609081337.J1ul7JmK-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.