From: Oscar Salvador <osalvador@suse.de>
To: David Hildenbrand <david@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Vlastimil Babka <vbabka@suse.cz>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Harry Yoo <harry.yoo@oracle.com>, Rakie Kim <rakie.kim@sk.com>,
Hyeonggon Yoo <42.hyeyoo@gmail.com>,
Joshua Hahn <joshua.hahnjy@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 03/10] mm,memory_hotplug: Implement numa node notifier
Date: Mon, 16 Jun 2025 13:45:05 +0200 [thread overview]
Message-ID: <aFADwYs9LcyK5tVn@localhost.localdomain> (raw)
In-Reply-To: <360f2f04-4542-4595-bf36-c45ed10335af@redhat.com>
On Mon, Jun 16, 2025 at 10:52:31AM +0200, David Hildenbrand wrote:
> Probably worth checking, to make sure we don't have accidental bugs in there
> ...
I did a quick sweep, and we should be cool since users of the node notifier
don't really use *_CANCEL* action. Only ADDED/REMOVED.
Now, users of memory notifier is a different story.
E.g: page_ext will call offline_page_ext to mark the section->page_ext invalid.
online_page_ext does:
base = alloc_page_ext(table_size, nid);
section->page_ext = (void *)base - page_ext_size * pfn;
This is fine, I think, offline_page_ext will not mark it as INVALID because
section->page_ext is NULL, so we just skip it.
This is just one example. I checked some others like kasan and hyperv and they
seem fine.
And anyway, the we could already hit this situation with MEM_* notifiers, so
nothing new.
I'll just make sure to document it so new users take this into account.
--
Oscar Salvador
SUSE Labs
next prev parent reply other threads:[~2025-06-16 11:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-09 9:21 [PATCH v6 00/10] Implement numa node notifier Oscar Salvador
2025-06-09 9:21 ` [PATCH v6 01/10] mm,slub: Do not special case N_NORMAL nodes for slab_nodes Oscar Salvador
2025-06-09 9:21 ` [PATCH v6 02/10] mm,memory_hotplug: Remove status_change_nid_normal and update documentation Oscar Salvador
2025-06-09 9:21 ` [PATCH v6 03/10] mm,memory_hotplug: Implement numa node notifier Oscar Salvador
2025-06-10 8:10 ` David Hildenbrand
2025-06-16 8:30 ` Oscar Salvador
2025-06-16 8:39 ` David Hildenbrand
2025-06-16 8:50 ` Oscar Salvador
2025-06-16 8:52 ` David Hildenbrand
2025-06-16 11:45 ` Oscar Salvador [this message]
2025-06-16 12:21 ` David Hildenbrand
2025-06-16 12:32 ` Oscar Salvador
2025-06-16 12:35 ` David Hildenbrand
2025-06-16 12:55 ` Oscar Salvador
2025-06-09 9:21 ` [PATCH v6 04/10] mm,slub: Use node-notifier instead of memory-notifier Oscar Salvador
2025-06-10 7:50 ` David Hildenbrand
2025-06-09 9:21 ` [PATCH v6 05/10] mm,memory-tiers: " Oscar Salvador
2025-06-10 7:51 ` David Hildenbrand
2025-06-09 9:21 ` [PATCH v6 06/10] drivers,cxl: " Oscar Salvador
2025-06-10 7:51 ` David Hildenbrand
2025-06-09 9:21 ` [PATCH v6 07/10] drivers,hmat: " Oscar Salvador
2025-06-10 7:52 ` David Hildenbrand
2025-06-09 9:21 ` [PATCH v6 08/10] kernel,cpuset: " Oscar Salvador
2025-06-09 9:21 ` [PATCH v6 09/10] mm,mempolicy: " Oscar Salvador
2025-06-10 7:52 ` David Hildenbrand
2025-06-09 9:21 ` [PATCH v6 10/10] mm,memory_hotplug: Drop status_change_nid parameter from memory_notify Oscar Salvador
2025-06-10 7:55 ` David Hildenbrand
2025-06-10 8:02 ` 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=aFADwYs9LcyK5tVn@localhost.localdomain \
--to=osalvador@suse.de \
--cc=42.hyeyoo@gmail.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=harry.yoo@oracle.com \
--cc=joshua.hahnjy@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rakie.kim@sk.com \
--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 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.