From: Gregory Price <gourry@gourry.net>
To: linux-mm@kvack.org
Cc: linux-cxl@vger.kernel.org, nvdimm@lists.linux.dev,
linux-kernel@vger.kernel.org, virtualization@lists.linux.dev,
kernel-team@meta.com, dan.j.williams@intel.com,
vishal.l.verma@intel.com, dave.jiang@intel.com, david@kernel.org,
mst@redhat.com, jasowang@redhat.com, xuanzhuo@linux.alibaba.com,
eperezma@redhat.com, osalvador@suse.de,
akpm@linux-foundation.org, Hannes Reinecke <hare@suse.de>
Subject: [PATCH 8/8] dax/kmem: add memory notifier to block external state changes
Date: Wed, 14 Jan 2026 03:52:00 -0500 [thread overview]
Message-ID: <20260114085201.3222597-9-gourry@gourry.net> (raw)
In-Reply-To: <20260114085201.3222597-1-gourry@gourry.net>
Add a memory notifier to prevent external operations from changing the
online/offline state of memory blocks managed by dax_kmem. This ensures
state changes only occur through the driver's hotplug sysfs interface,
providing consistent state tracking and preventing races with auto-online
policies or direct memory block sysfs manipulation.
The notifier uses a transition protocol with memory barriers:
- Before initiating a state change, set target_state then in_transition
- Use a barrier to ensure target_state is visible before in_transition
- The notifier checks in_transition, then uses barrier before reading
target_state to ensure proper ordering on weakly-ordered architectures
The notifier callback:
- Returns NOTIFY_DONE for non-overlapping memory (not our concern)
- Returns NOTIFY_BAD if in_transition is false (block external ops)
- Validates the memory event matches target_state (MEM_GOING_ONLINE
for online operations, MEM_GOING_OFFLINE for offline/unplug)
- Returns NOTIFY_OK only for driver-initiated operations with matching
target_state
This prevents scenarios where:
- Auto-online policies re-online memory the driver is trying to offline
- Users manually change memory state via /sys/devices/system/memory/
- Other kernel subsystems interfere with driver-managed memory state
Suggested-by: Hannes Reinecke <hare@suse.de>
Suggested-by: David Hildenbrand <david@kernel.org>
Signed-off-by: Gregory Price <gourry@gourry.net>
---
drivers/dax/kmem.c | 164 +++++++++++++++++++++++++++++++++++++++++++--
1 file changed, 160 insertions(+), 4 deletions(-)
diff --git a/drivers/dax/kmem.c b/drivers/dax/kmem.c
index 6d73c44e4e08..b604da8b3fe1 100644
--- a/drivers/dax/kmem.c
+++ b/drivers/dax/kmem.c
@@ -53,6 +53,9 @@ struct dax_kmem_data {
struct dev_dax *dev_dax;
int state;
struct mutex lock; /* protects hotplug state transitions */
+ bool in_transition;
+ int target_state;
+ struct notifier_block mem_nb;
struct resource *res[];
};
@@ -71,6 +74,116 @@ static void kmem_put_memory_types(void)
mt_put_memory_types(&kmem_memory_types);
}
+/**
+ * dax_kmem_start_transition - begin a driver-initiated state transition
+ * @data: the dax_kmem_data structure
+ * @target: the target state (MMOP_ONLINE, MMOP_ONLINE_MOVABLE, or MMOP_OFFLINE)
+ *
+ * Sets up state for a driver-initiated memory operation. The memory notifier
+ * will only allow operations that match this target state while in transition.
+ * Uses store-release to ensure target_state is visible before in_transition.
+ */
+static void dax_kmem_start_transition(struct dax_kmem_data *data, int target)
+{
+ data->target_state = target;
+ smp_store_release(&data->in_transition, true);
+}
+
+/**
+ * dax_kmem_end_transition - end a driver-initiated state transition
+ * @data: the dax_kmem_data structure
+ *
+ * Clears the in_transition flag after a state change completes or aborts.
+ */
+static void dax_kmem_end_transition(struct dax_kmem_data *data)
+{
+ WRITE_ONCE(data->in_transition, false);
+}
+
+/**
+ * dax_kmem_overlaps_range - check if a memory range overlaps with this device
+ * @data: the dax_kmem_data structure
+ * @start: start physical address of the range to check
+ * @size: size of the range to check
+ *
+ * Returns true if the range overlaps with any of the device's memory ranges.
+ */
+static bool dax_kmem_overlaps_range(struct dax_kmem_data *data,
+ u64 start, u64 size)
+{
+ struct dev_dax *dev_dax = data->dev_dax;
+ int i;
+
+ for (i = 0; i < dev_dax->nr_range; i++) {
+ struct range range;
+ struct range check = DEFINE_RANGE(start, start + size - 1);
+
+ if (dax_kmem_range(dev_dax, i, &range))
+ continue;
+
+ if (!data->res[i])
+ continue;
+
+ if (range_overlaps(&range, &check))
+ return true;
+ }
+ return false;
+}
+
+/**
+ * dax_kmem_memory_notifier_cb - memory notifier callback for dax kmem
+ * @nb: the notifier block (embedded in dax_kmem_data)
+ * @action: the memory event (MEM_GOING_ONLINE, MEM_GOING_OFFLINE, etc.)
+ * @arg: pointer to memory_notify structure
+ *
+ * This callback prevents external operations (e.g., from sysfs or auto-online
+ * policies) on memory blocks managed by dax_kmem. Only operations initiated
+ * by the driver itself (via the hotplug sysfs interface) are allowed.
+ *
+ * Returns NOTIFY_OK to allow the operation, NOTIFY_BAD to block it,
+ * or NOTIFY_DONE if the memory doesn't belong to this device.
+ */
+static int dax_kmem_memory_notifier_cb(struct notifier_block *nb,
+ unsigned long action, void *arg)
+{
+ struct dax_kmem_data *data = container_of(nb, struct dax_kmem_data,
+ mem_nb);
+ struct memory_notify *mhp = arg;
+ const u64 start = PFN_PHYS(mhp->start_pfn);
+ const u64 size = PFN_PHYS(mhp->nr_pages);
+
+ /* Only interested in going online/offline events */
+ if (action != MEM_GOING_ONLINE && action != MEM_GOING_OFFLINE)
+ return NOTIFY_DONE;
+
+ /* Check if this memory belongs to our device */
+ if (!dax_kmem_overlaps_range(data, start, size))
+ return NOTIFY_DONE;
+
+ /*
+ * Block all operations unless we're in a driver-initiated transition.
+ * When in_transition is set, only allow operations that match our
+ * target_state to prevent races with external operations.
+ *
+ * Use load-acquire to pair with the store-release in
+ * dax_kmem_start_transition(), ensuring target_state is visible.
+ */
+ if (!smp_load_acquire(&data->in_transition))
+ return NOTIFY_BAD;
+
+ /* Online operations expect MEM_GOING_ONLINE */
+ if (action == MEM_GOING_ONLINE &&
+ (data->target_state == MMOP_ONLINE ||
+ data->target_state == MMOP_ONLINE_MOVABLE))
+ return NOTIFY_OK;
+
+ /* Offline/hotremove operations expect MEM_GOING_OFFLINE */
+ if (action == MEM_GOING_OFFLINE && data->target_state == MMOP_OFFLINE)
+ return NOTIFY_OK;
+
+ return NOTIFY_BAD;
+}
+
/**
* dax_kmem_do_hotplug - hotplug memory for dax kmem device
* @dev_dax: the dev_dax instance
@@ -375,11 +488,27 @@ static ssize_t hotplug_store(struct device *dev, struct device_attribute *attr,
if (data->state == online_type)
return len;
+ /*
+ * Start transition with target_state for the notifier.
+ * For unplug, use MMOP_OFFLINE since memory goes offline before removal.
+ */
+ if (online_type == DAX_KMEM_UNPLUGGED || online_type == MMOP_OFFLINE)
+ dax_kmem_start_transition(data, MMOP_OFFLINE);
+ else
+ dax_kmem_start_transition(data, online_type);
+
if (online_type == DAX_KMEM_UNPLUGGED) {
+ int expected = 0;
+
+ for (rc = 0; rc < dev_dax->nr_range; rc++)
+ if (data->res[rc])
+ expected++;
+
rc = dax_kmem_do_hotremove(dev_dax, data);
- if (rc < 0) {
+ dax_kmem_end_transition(data);
+ if (rc < expected) {
dev_warn(dev, "hotplug state is inconsistent\n");
- return rc;
+ return rc == 0 ? -EBUSY : -EIO;
}
data->state = DAX_KMEM_UNPLUGGED;
return len;
@@ -387,9 +516,12 @@ static ssize_t hotplug_store(struct device *dev, struct device_attribute *attr,
if (online_type == MMOP_OFFLINE) {
/* Can only offline from an online state */
- if (data->state != MMOP_ONLINE && data->state != MMOP_ONLINE_MOVABLE)
+ if (data->state != MMOP_ONLINE && data->state != MMOP_ONLINE_MOVABLE) {
+ dax_kmem_end_transition(data);
return -EINVAL;
+ }
rc = dax_kmem_do_offline(dev_dax, data);
+ dax_kmem_end_transition(data);
if (rc < 0) {
dev_warn(dev, "hotplug state is inconsistent\n");
return rc;
@@ -401,14 +533,18 @@ static ssize_t hotplug_store(struct device *dev, struct device_attribute *attr,
/* online_type is MMOP_ONLINE or MMOP_ONLINE_MOVABLE */
/* Cannot switch between online types without offlining first */
- if (data->state == MMOP_ONLINE || data->state == MMOP_ONLINE_MOVABLE)
+ if (data->state == MMOP_ONLINE || data->state == MMOP_ONLINE_MOVABLE) {
+ dax_kmem_end_transition(data);
return -EBUSY;
+ }
if (data->state == MMOP_OFFLINE)
rc = dax_kmem_do_online(dev_dax, data, online_type);
else
rc = dax_kmem_do_hotplug(dev_dax, data, online_type);
+ dax_kmem_end_transition(data);
+
if (rc < 0)
return rc;
@@ -490,12 +626,25 @@ static int dev_dax_kmem_probe(struct dev_dax *dev_dax)
dev_set_drvdata(dev, data);
+ /* Register memory notifier to block external operations */
+ data->mem_nb.notifier_call = dax_kmem_memory_notifier_cb;
+ rc = register_memory_notifier(&data->mem_nb);
+ if (rc) {
+ dev_warn(dev, "failed to register memory notifier\n");
+ goto err_notifier;
+ }
+
/*
* Hotplug the memory using the system default online policy.
* This preserves backwards compatibility for existing users who
* rely on auto-online behavior.
+ *
+ * Start transition with resolved system default since the notifier
+ * validates the operation type matches.
*/
+ dax_kmem_start_transition(data, mhp_get_default_online_type());
rc = dax_kmem_do_hotplug(dev_dax, data, MMOP_SYSTEM_DEFAULT);
+ dax_kmem_end_transition(data);
if (rc < 0)
goto err_hotplug;
/*
@@ -511,6 +660,8 @@ static int dev_dax_kmem_probe(struct dev_dax *dev_dax)
return 0;
err_hotplug:
+ unregister_memory_notifier(&data->mem_nb);
+err_notifier:
dev_set_drvdata(dev, NULL);
memory_group_unregister(data->mgid);
err_reg_mgid:
@@ -538,12 +689,15 @@ static void dev_dax_kmem_remove(struct dev_dax *dev_dax)
* there is no way to hotremove this memory until reboot because device
* unbind will succeed even if we return failure.
*/
+ dax_kmem_start_transition(data, MMOP_OFFLINE);
success = dax_kmem_do_hotremove(dev_dax, data);
+ dax_kmem_end_transition(data);
if (success < dev_dax->nr_range) {
dev_err(dev, "Hotplug regions stuck online until reboot\n");
return;
}
+ unregister_memory_notifier(&data->mem_nb);
memory_group_unregister(data->mgid);
kfree(data->res_name);
kfree(data);
@@ -561,8 +715,10 @@ static void dev_dax_kmem_remove(struct dev_dax *dev_dax)
static void dev_dax_kmem_remove(struct dev_dax *dev_dax)
{
struct device *dev = &dev_dax->dev;
+ struct dax_kmem_data *data = dev_get_drvdata(dev);
device_remove_file(dev, &dev_attr_hotplug);
+ unregister_memory_notifier(&data->mem_nb);
/*
* Without hotremove purposely leak the request_mem_region() for the
--
2.52.0
next prev parent reply other threads:[~2026-01-14 8:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 8:51 Subject: [PATCH 0/8] dax/kmem: add runtime hotplug state control Gregory Price
2026-01-14 8:51 ` [PATCH 1/8] mm/memory_hotplug: pass online_type to online_memory_block() via arg Gregory Price
2026-01-14 9:46 ` David Hildenbrand (Red Hat)
2026-01-14 8:51 ` [PATCH 2/8] mm/memory_hotplug: extract __add_memory_resource() and __offline_memory() Gregory Price
2026-01-14 10:14 ` David Hildenbrand (Red Hat)
2026-01-14 8:51 ` [PATCH 3/8] mm/memory_hotplug: add APIs for explicit online type control Gregory Price
2026-01-14 10:21 ` David Hildenbrand (Red Hat)
2026-01-14 8:51 ` [PATCH 4/8] mm/memory_hotplug: return online type from add_memory_driver_managed() Gregory Price
2026-01-14 10:49 ` David Hildenbrand (Red Hat)
2026-01-14 8:51 ` [PATCH 5/8] dax/kmem: extract hotplug/hotremove helper functions Gregory Price
2026-01-14 8:51 ` [PATCH 6/8] dax/kmem: add online/offline " Gregory Price
2026-01-14 8:51 ` [PATCH 7/8] dax/kmem: add sysfs interface for runtime hotplug state control Gregory Price
2026-01-14 10:55 ` David Hildenbrand (Red Hat)
2026-01-14 8:52 ` Gregory Price [this message]
2026-01-14 9:44 ` [PATCH 8/8] dax/kmem: add memory notifier to block external state changes David Hildenbrand (Red Hat)
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=20260114085201.3222597-9-gourry@gourry.net \
--to=gourry@gourry.net \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=david@kernel.org \
--cc=eperezma@redhat.com \
--cc=hare@suse.de \
--cc=jasowang@redhat.com \
--cc=kernel-team@meta.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mst@redhat.com \
--cc=nvdimm@lists.linux.dev \
--cc=osalvador@suse.de \
--cc=virtualization@lists.linux.dev \
--cc=vishal.l.verma@intel.com \
--cc=xuanzhuo@linux.alibaba.com \
/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