linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Oscar Salvador <osalvador@suse.de>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Memory Management List <linux-mm@kvack.org>,
	Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	Harry Yoo <harry.yoo@oracle.com>,
	Vlastimil Babka <vbabka@suse.cz>
Subject: [akpm-mm:mm-new 33/59] kernel/cgroup/cpuset.c:4054:undefined reference to `register_node_notifier'
Date: Wed, 4 Jun 2025 20:35:10 +0800	[thread overview]
Message-ID: <202506042006.QuupA03H-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-new
head:   80bb0b2983e95be26d929303d589276875c8900a
commit: 24bc7e1b9a3e0062e4bcde941a76c7dbe5516401 [33/59] mm,memory_hotplug: implement numa node notifier
config: s390-randconfig-001-20250604 (https://download.01.org/0day-ci/archive/20250604/202506042006.QuupA03H-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250604/202506042006.QuupA03H-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/202506042006.QuupA03H-lkp@intel.com/

All errors (new ones prefixed by >>):

   s390x-linux-ld: kernel/cgroup/cpuset.o: in function `cpuset_init_smp':
>> kernel/cgroup/cpuset.c:4054:(.init.text+0x402): undefined reference to `register_node_notifier'
   s390x-linux-ld: mm/memory_hotplug.o: in function `online_pages':
>> mm/memory_hotplug.c:1243:(.text+0x6928): undefined reference to `node_notify'
   s390x-linux-ld: mm/slub.o: in function `kmem_cache_init':
>> mm/slub.c:6300:(.init.text+0x506): undefined reference to `register_node_notifier'


vim +4054 kernel/cgroup/cpuset.c

  4036	
  4037	/**
  4038	 * cpuset_init_smp - initialize cpus_allowed
  4039	 *
  4040	 * Description: Finish top cpuset after cpu, node maps are initialized
  4041	 */
  4042	void __init cpuset_init_smp(void)
  4043	{
  4044		/*
  4045		 * cpus_allowd/mems_allowed set to v2 values in the initial
  4046		 * cpuset_bind() call will be reset to v1 values in another
  4047		 * cpuset_bind() call when v1 cpuset is mounted.
  4048		 */
  4049		top_cpuset.old_mems_allowed = top_cpuset.mems_allowed;
  4050	
  4051		cpumask_copy(top_cpuset.effective_cpus, cpu_active_mask);
  4052		top_cpuset.effective_mems = node_states[N_MEMORY];
  4053	
> 4054		hotplug_node_notifier(cpuset_track_online_nodes, CPUSET_CALLBACK_PRI);
  4055	
  4056		cpuset_migrate_mm_wq = alloc_ordered_workqueue("cpuset_migrate_mm", 0);
  4057		BUG_ON(!cpuset_migrate_mm_wq);
  4058	}
  4059	

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


                 reply	other threads:[~2025-06-04 12:36 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=202506042006.QuupA03H-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=harry.yoo@oracle.com \
    --cc=linux-mm@kvack.org \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=osalvador@suse.de \
    --cc=vbabka@suse.cz \
    /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