From: Ira Weiny <ira.weiny@intel.com>
To: Vishal Verma <vishal.l.verma@intel.com>
Cc: Dave Jiang <dave.jiang@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
nvdimm@lists.linux.dev, linux-cxl@vger.kernel.org,
Ira Weiny <ira.weiny@intel.com>
Subject: [PATCH ndctl RESEND 2/2] cxl/region: Fix memory device teardown in disable-region
Date: Thu, 30 Nov 2023 20:06:14 -0800 [thread overview]
Message-ID: <20231130-fix-region-destroy-v1-2-7f916d2bd379@intel.com> (raw)
In-Reply-To: <20231130-fix-region-destroy-v1-0-7f916d2bd379@intel.com>
When a region is requested to be disabled, memory devices are normally
automatically torn down. Commit 9399aa667ab0 prevents tear down if
memory is online without a force flag. However, daxctl_dev_get_memory()
may return NULL if the memory device in question is not system-ram
capable as is the case for a region with only devdax devices. Such
devices do not need to be off-lined explicitly.
Skip non-system-ram devices rather than error the operation.
Fixes: 9399aa667ab0 ("cxl/region: Add -f option for disable-region")
Cc: Dave Jiang <dave.jiang@intel.com>
Signed-off-by: Ira Weiny <ira.weiny@intel.com>
---
cxl/region.c | 3 +++
daxctl/lib/libdaxctl.c | 4 ++--
daxctl/lib/libdaxctl.sym | 5 +++++
daxctl/libdaxctl.h | 1 +
4 files changed, 11 insertions(+), 2 deletions(-)
diff --git a/cxl/region.c b/cxl/region.c
index 5cbbf2749e2d..44ac76b001e9 100644
--- a/cxl/region.c
+++ b/cxl/region.c
@@ -805,6 +805,9 @@ static int disable_region(struct cxl_region *region)
goto out;
daxctl_dev_foreach(dax_region, dev) {
+ if (!daxctl_dev_is_system_ram_capable(dev))
+ continue;
+
mem = daxctl_dev_get_memory(dev);
if (!mem)
return -ENXIO;
diff --git a/daxctl/lib/libdaxctl.c b/daxctl/lib/libdaxctl.c
index 4f9aba0b09f2..9fbefe2e8329 100644
--- a/daxctl/lib/libdaxctl.c
+++ b/daxctl/lib/libdaxctl.c
@@ -385,7 +385,7 @@ static bool device_model_is_dax_bus(struct daxctl_dev *dev)
return false;
}
-static int dev_is_system_ram_capable(struct daxctl_dev *dev)
+DAXCTL_EXPORT int daxctl_dev_is_system_ram_capable(struct daxctl_dev *dev)
{
const char *devname = daxctl_dev_get_devname(dev);
struct daxctl_ctx *ctx = daxctl_dev_get_ctx(dev);
@@ -432,7 +432,7 @@ static struct daxctl_memory *daxctl_dev_alloc_mem(struct daxctl_dev *dev)
char buf[SYSFS_ATTR_SIZE];
int node_num;
- if (!dev_is_system_ram_capable(dev))
+ if (!daxctl_dev_is_system_ram_capable(dev))
return NULL;
mem = calloc(1, sizeof(*mem));
diff --git a/daxctl/lib/libdaxctl.sym b/daxctl/lib/libdaxctl.sym
index fe68fd0a9cde..309881196c86 100644
--- a/daxctl/lib/libdaxctl.sym
+++ b/daxctl/lib/libdaxctl.sym
@@ -99,3 +99,8 @@ global:
daxctl_set_config_path;
daxctl_get_config_path;
} LIBDAXCTL_8;
+
+LIBDAXCTL_10 {
+global:
+ daxctl_dev_is_system_ram_capable;
+} LIBDAXCTL_9;
diff --git a/daxctl/libdaxctl.h b/daxctl/libdaxctl.h
index 6876037a9427..53c6bbdae5c3 100644
--- a/daxctl/libdaxctl.h
+++ b/daxctl/libdaxctl.h
@@ -77,6 +77,7 @@ int daxctl_dev_will_auto_online_memory(struct daxctl_dev *dev);
int daxctl_dev_has_online_memory(struct daxctl_dev *dev);
struct daxctl_memory;
+int daxctl_dev_is_system_ram_capable(struct daxctl_dev *dev);
struct daxctl_memory *daxctl_dev_get_memory(struct daxctl_dev *dev);
struct daxctl_dev *daxctl_memory_get_dev(struct daxctl_memory *mem);
const char *daxctl_memory_get_node_path(struct daxctl_memory *mem);
--
2.42.0
next prev parent reply other threads:[~2023-12-01 4:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 4:06 [PATCH ndctl RESEND 0/2] ndctl: Fix ups for region destroy Ira Weiny
2023-12-01 4:06 ` [PATCH ndctl RESEND 1/2] ndctl/test: Add destroy region test Ira Weiny
2023-12-01 17:40 ` Dave Jiang
2023-12-01 19:39 ` Alison Schofield
2023-12-04 18:05 ` Ira Weiny
2023-12-04 20:42 ` Verma, Vishal L
2023-12-05 21:22 ` Ira Weiny
2023-12-06 3:00 ` Verma, Vishal L
2023-12-01 4:06 ` Ira Weiny [this message]
2023-12-01 17:39 ` [PATCH ndctl RESEND 2/2] cxl/region: Fix memory device teardown in disable-region Dave Jiang
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=20231130-fix-region-destroy-v1-2-7f916d2bd379@intel.com \
--to=ira.weiny@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=vishal.l.verma@intel.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