From: Dave Jiang <dave.jiang@intel.com>
To: Davidlohr Bueso <dave@stgolabs.net>, dan.j.williams@intel.com
Cc: jonathan.cameron@huawei.com, ira.weiny@intel.com,
fan.ni@samsung.com, a.manzanares@samsung.com,
linux-cxl@vger.kernel.org
Subject: Re: [PATCH 2/7] cxl/security: Add security state sysfs ABI
Date: Tue, 28 Feb 2023 09:47:40 -0700 [thread overview]
Message-ID: <44d17cd5-a580-1f1d-980c-137834ed6125@intel.com> (raw)
In-Reply-To: <20230224194652.1990604-3-dave@stgolabs.net>
On 2/24/23 12:46 PM, Davidlohr Bueso wrote:
> This adds the sysfs memdev's security/ directory with
> a single 'state' file, which is always visible. In the
> case of unsupported security features, this will show
> disabled.
>
> Signed-off-by: Davidlohr Bueso <dave@stgolabs.net>
I don't have strong opinion on whether the state attrib should be
visible if there's no security support, but this deviates from the
nvdimm security state behavior.
Reviewed-by: Dave Jiang <dave.jiang@intel.com>
> ---
> Documentation/ABI/testing/sysfs-bus-cxl | 8 ++++
> drivers/cxl/core/memdev.c | 49 +++++++++++++++++++++++++
> 2 files changed, 57 insertions(+)
>
> diff --git a/Documentation/ABI/testing/sysfs-bus-cxl b/Documentation/ABI/testing/sysfs-bus-cxl
> index 3acf2f17a73f..e9c432a5a841 100644
> --- a/Documentation/ABI/testing/sysfs-bus-cxl
> +++ b/Documentation/ABI/testing/sysfs-bus-cxl
> @@ -57,6 +57,14 @@ Description:
> host PCI device for this memory device, emit the CPU node
> affinity for this device.
>
> +What: /sys/bus/cxl/devices/memX/security/state
> +Date: February, 2023
> +KernelVersion: v6.4
> +Contact: linux-cxl@vger.kernel.org
> +Description:
> + (RO) The security state for that device. The following states
> + are available: frozen, locked, unlocked and disabled (which
> + is also the case for any unsupported security features).
>
> What: /sys/bus/cxl/devices/*/devtype
> Date: June, 2021
> diff --git a/drivers/cxl/core/memdev.c b/drivers/cxl/core/memdev.c
> index 0af8856936dc..47cc625bb1b0 100644
> --- a/drivers/cxl/core/memdev.c
> +++ b/drivers/cxl/core/memdev.c
> @@ -1,6 +1,7 @@
> // SPDX-License-Identifier: GPL-2.0-only
> /* Copyright(c) 2020 Intel Corporation. */
>
> +#include <linux/memregion.h>
> #include <linux/device.h>
> #include <linux/slab.h>
> #include <linux/idr.h>
> @@ -89,6 +90,43 @@ static ssize_t pmem_size_show(struct device *dev, struct device_attribute *attr,
> static struct device_attribute dev_attr_pmem_size =
> __ATTR(size, 0444, pmem_size_show, NULL);
>
> +static ssize_t security_state_show(struct device *dev,
> + struct device_attribute *attr, char *buf)
> +{
> + u32 sec_out;
> + struct cxl_memdev *cxlmd = to_cxl_memdev(dev);
> + struct cxl_dev_state *cxlds = cxlmd->cxlds;
> + struct cxl_get_security_output {
> + __le32 flags;
> + } out;
> + struct cxl_mbox_cmd mbox_cmd = {
> + .opcode = CXL_MBOX_OP_GET_SECURITY_STATE,
> + .payload_out = &out,
> + .size_out = sizeof(out),
> + };
> +
> + if (!cpu_cache_has_invalidate_memregion())
> + goto disabled;
> +
> + if (cxl_internal_send_cmd(cxlds, &mbox_cmd) < 0)
> + goto disabled;
> +
> + sec_out = le32_to_cpu(out.flags);
> + if (!(sec_out & CXL_PMEM_SEC_STATE_USER_PASS_SET))
> + goto disabled;
> + if (sec_out & CXL_PMEM_SEC_STATE_FROZEN)
> + return sysfs_emit(buf, "frozen\n");
> + if (sec_out & CXL_PMEM_SEC_STATE_LOCKED)
> + return sysfs_emit(buf, "locked\n");
> + else
> + return sysfs_emit(buf, "unlocked\n");
> +disabled:
> + return sysfs_emit(buf, "disabled\n");
> +}
> +
> +static struct device_attribute dev_attr_security_state =
> + __ATTR(state, 0444, security_state_show, NULL);
> +
> static ssize_t serial_show(struct device *dev, struct device_attribute *attr,
> char *buf)
> {
> @@ -148,10 +186,21 @@ static struct attribute_group cxl_memdev_pmem_attribute_group = {
> .attrs = cxl_memdev_pmem_attributes,
> };
>
> +static struct attribute *cxl_memdev_security_attributes[] = {
> + &dev_attr_security_state.attr,
> + NULL,
> +};
> +
> +static struct attribute_group cxl_memdev_security_attribute_group = {
> + .name = "security",
> + .attrs = cxl_memdev_security_attributes,
> +};
> +
> static const struct attribute_group *cxl_memdev_attribute_groups[] = {
> &cxl_memdev_attribute_group,
> &cxl_memdev_ram_attribute_group,
> &cxl_memdev_pmem_attribute_group,
> + &cxl_memdev_security_attribute_group,
> NULL,
> };
>
next prev parent reply other threads:[~2023-02-28 16:48 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 19:46 [PATCH v3 0/7] cxl: Background cmds and device sanitation Davidlohr Bueso
2023-02-24 19:25 ` Davidlohr Bueso
2023-02-24 19:46 ` [PATCH 1/7] cxl/mbox: Add background cmd handling machinery Davidlohr Bueso
2023-02-28 16:27 ` Dave Jiang
2023-02-28 20:18 ` Davidlohr Bueso
2023-02-28 23:35 ` Dave Jiang
2023-03-27 21:57 ` Dan Williams
2023-02-24 19:46 ` [PATCH 2/7] cxl/security: Add security state sysfs ABI Davidlohr Bueso
2023-02-28 16:47 ` Dave Jiang [this message]
2023-03-28 1:11 ` Dan Williams
2023-02-24 19:46 ` [PATCH 3/7] cxl/region: Add cxl_memdev_active_region() Davidlohr Bueso
2023-02-27 3:46 ` Alison Schofield
2023-02-28 20:26 ` Davidlohr Bueso
2023-02-28 23:20 ` Fan Ni
2023-03-28 1:15 ` Dan Williams
2023-02-24 19:46 ` [PATCH 4/7] cxl/mem: Support Sanitation Davidlohr Bueso
2023-02-28 17:28 ` Dave Jiang
2023-02-28 20:22 ` Davidlohr Bueso
2023-03-28 6:26 ` Dan Williams
2023-04-05 21:06 ` Davidlohr Bueso
2023-04-05 22:24 ` Dan Williams
2023-02-24 19:46 ` [PATCH 5/7] cxl/test: Add "Sanitize" opcode support Davidlohr Bueso
2023-02-28 18:03 ` Dave Jiang
2023-02-24 19:46 ` [PATCH 6/7] cxl/mem: Support Secure Erase Davidlohr Bueso
2023-02-28 18:31 ` Dave Jiang
2023-02-24 19:46 ` [PATCH 7/7] cxl/test: Add "Secure Erase" opcode support Davidlohr Bueso
2023-02-28 18:36 ` Dave Jiang
2023-03-22 0:05 ` [PATCH v3 0/7] cxl: Background cmds and device sanitation Davidlohr Bueso
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=44d17cd5-a580-1f1d-980c-137834ed6125@intel.com \
--to=dave.jiang@intel.com \
--cc=a.manzanares@samsung.com \
--cc=dan.j.williams@intel.com \
--cc=dave@stgolabs.net \
--cc=fan.ni@samsung.com \
--cc=ira.weiny@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
/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