From: Oscar Salvador <osalvador@suse.de>
To: kernel test robot <lkp@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
David Hildenbrand <david@redhat.com>,
linux-kernel@vger.kernel.org, Vlastimil Babka <vbabka@suse.cz>,
Harry Yoo <harry.yoo@oracle.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
linux-cxl@vger.kernel.org
Subject: Re: [PATCH v2 2/3] mm,memory_hotplug: Implement numa node notifier
Date: Wed, 9 Apr 2025 18:58:04 +0200 [thread overview]
Message-ID: <Z_anHMHgQQM3y-w2@localhost.localdomain> (raw)
In-Reply-To: <202504092104.MyHeSV43-lkp@intel.com>
On Wed, Apr 09, 2025 at 09:44:52PM +0800, kernel test robot wrote:
> Hi Oscar,
>
> kernel test robot noticed the following build errors:
...
> >> drivers/base/node.c:115:5: error: redefinition of 'register_node_notifier'
> 115 | int register_node_notifier(struct notifier_block *nb)
> | ^
> include/linux/memory.h:172:19: note: previous definition is here
> 172 | static inline int register_node_notifier(struct notifier_block *nb)
> | ^
> >> drivers/base/node.c:121:6: error: redefinition of 'unregister_node_notifier'
> 121 | void unregister_node_notifier(struct notifier_block *nb)
> | ^
> include/linux/memory.h:176:20: note: previous definition is here
> 176 | static inline void unregister_node_notifier(struct notifier_block *nb)
> | ^
> >> drivers/base/node.c:127:5: error: redefinition of 'node_notify'
> 127 | int node_notify(unsigned long val, void *v)
> | ^
> include/linux/memory.h:179:19: note: previous definition is here
> 179 | static inline int node_notify(unsigned long val, void *v)
> | ^
> 3 errors generated.
Ah, I see. When CONFIG_MEMORY_HOTPLUG=n those come into play.
That is not a problem for the memory-notify thing because drivers/base/memory.c
gets compiled IFF CONFIG_MEMORY_HOTPLUG=y.
I am thinking two ways to fix this:
1) Move the code for node-notify to drivers/base/memory.c
2) Surround those functions within a
#ifdef CONFIG_MEMORY_HOTPLUG
...
#endif
Thoughts? I lean towards option #2 as it looks cleaner to me:
diff --git a/drivers/base/node.c b/drivers/base/node.c
index 182c71dfb5b8..3b084d71888a 100644
--- a/drivers/base/node.c
+++ b/drivers/base/node.c
@@ -110,6 +110,7 @@ static const struct attribute_group *node_access_node_groups[] = {
NULL,
};
+#ifdef CONFIG_MEMORY_HOTPLUG
static BLOCKING_NOTIFIER_HEAD(node_chain);
int register_node_notifier(struct notifier_block *nb)
@@ -128,6 +129,7 @@ int node_notify(unsigned long val, void *v)
{
return blocking_notifier_call_chain(&node_chain, val, v);
}
+#endif
static void node_remove_accesses(struct node *node)
{
--
Oscar Salvador
SUSE Labs
next prev parent reply other threads:[~2025-04-09 16:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 8:41 [PATCH v2 0/3] " Oscar Salvador
2025-04-08 8:41 ` [PATCH v2 1/3] mm,slub: Do not special case N_NORMAL nodes for slab_nodes Oscar Salvador
2025-04-08 10:17 ` David Hildenbrand
2025-04-08 12:49 ` Oscar Salvador
2025-04-08 15:15 ` Harry Yoo
2025-04-08 14:18 ` Harry Yoo
2025-04-08 14:25 ` David Hildenbrand
2025-04-08 14:54 ` Harry Yoo
2025-04-08 17:55 ` Vlastimil Babka
2025-04-08 18:18 ` David Hildenbrand
2025-04-30 8:47 ` Oscar Salvador
2025-04-30 8:57 ` Vlastimil Babka
2025-04-30 9:02 ` David Hildenbrand
2025-04-08 8:41 ` [PATCH v2 2/3] mm,memory_hotplug: Implement numa node notifier Oscar Salvador
2025-04-09 13:44 ` kernel test robot
2025-04-09 16:58 ` Oscar Salvador [this message]
2025-04-08 8:41 ` [PATCH v2 3/3] mm,memory_hotplug: Rename status_change_nid parameter in memory_notify Oscar Salvador
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=Z_anHMHgQQM3y-w2@localhost.localdomain \
--to=osalvador@suse.de \
--cc=Jonathan.Cameron@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=harry.yoo@oracle.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--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