From: Ben Cheatham <benjamin.cheatham@amd.com>
To: Dave Jiang <dave.jiang@intel.com>,
linux-cxl@vger.kernel.org, nvdimm@lists.linux.dev
Cc: dan.j.williams@intel.com, ira.weiny@intel.com,
vishal.l.verma@intel.com, alison.schofield@intel.com,
Jonathan.Cameron@huawei.com, dave@stgolabs.net
Subject: Re: [PATCH v4 13/18] nvdimm/cxl/pmem: Add support for master passphrase disable security command
Date: Mon, 14 Nov 2022 16:27:14 -0600 [thread overview]
Message-ID: <1cc14f3f-6500-778a-087c-e7601f82adf3@amd.com> (raw)
In-Reply-To: <166845805988.2496228.8804764265372893076.stgit@djiang5-desk3.ch.intel.com>
On 11/14/22 2:34 PM, Dave Jiang wrote:
> The original nvdimm_security_ops ->disable() only supports user passphrase
> for security disable. The CXL spec introduced the disabling of master
> passphrase. Add a ->disable_master() callback to support this new operation
> and leaving the old ->disable() mechanism alone. A "disable_master" command
> is added for the sysfs attribute in order to allow command to be issued
> from userspace. ndctl will need enabling in order to utilize this new
> operation.
>
> Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> Signed-off-by: Dave Jiang <dave.jiang@intel.com>
> ---
> drivers/cxl/security.c | 20 ++++++++++++++++++--
> drivers/nvdimm/security.c | 33 ++++++++++++++++++++++++++-------
> include/linux/libnvdimm.h | 2 ++
> 3 files changed, 46 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/cxl/security.c b/drivers/cxl/security.c
> index 631a474939d6..f4df7d38e4cd 100644
> --- a/drivers/cxl/security.c
> +++ b/drivers/cxl/security.c
> @@ -71,8 +71,9 @@ static int cxl_pmem_security_change_key(struct nvdimm *nvdimm,
> return rc;
> }
>
> -static int cxl_pmem_security_disable(struct nvdimm *nvdimm,
> - const struct nvdimm_key_data *key_data)
> +static int __cxl_pmem_security_disable(struct nvdimm *nvdimm,
> + const struct nvdimm_key_data *key_data,
> + enum nvdimm_passphrase_type ptype)
> {
> struct cxl_nvdimm *cxl_nvd = nvdimm_provider_data(nvdimm);
> struct cxl_memdev *cxlmd = cxl_nvd->cxlmd;
> @@ -88,6 +89,8 @@ static int cxl_pmem_security_disable(struct nvdimm *nvdimm,
> * will only support disable of user passphrase. The disable master passphrase
> * ability will need to be added as a new callback.
> */
> + dis_pass.type = ptype == NVDIMM_MASTER ?
> + CXL_PMEM_SEC_PASS_MASTER : CXL_PMEM_SEC_PASS_USER;
> dis_pass.type = CXL_PMEM_SEC_PASS_USER;
Hey Dave,
I noticed that you are overwriting dis_pass.type with
CXL_PMEM_SEC_PASS_USER after your added change here. I imagine that's
not intentional considering the rest of the work in this patch!
Ben
> memcpy(dis_pass.pass, key_data->data, NVDIMM_PASSPHRASE_LEN);
>
> @@ -96,6 +99,18 @@ static int cxl_pmem_security_disable(struct nvdimm *nvdimm,
> return rc;
> }
>
> +static int cxl_pmem_security_disable(struct nvdimm *nvdimm,
> + const struct nvdimm_key_data *key_data)
> +{
> + return __cxl_pmem_security_disable(nvdimm, key_data, NVDIMM_USER);
> +}
> +
> +static int cxl_pmem_security_disable_master(struct nvdimm *nvdimm,
> + const struct nvdimm_key_data *key_data)
> +{
> + return __cxl_pmem_security_disable(nvdimm, key_data, NVDIMM_MASTER);
> +}
> +
> static int cxl_pmem_security_freeze(struct nvdimm *nvdimm)
> {
> struct cxl_nvdimm *cxl_nvd = nvdimm_provider_data(nvdimm);
> @@ -163,6 +178,7 @@ static const struct nvdimm_security_ops __cxl_security_ops = {
> .freeze = cxl_pmem_security_freeze,
> .unlock = cxl_pmem_security_unlock,
> .erase = cxl_pmem_security_passphrase_erase,
> + .disable_master = cxl_pmem_security_disable_master,
> };
>
> const struct nvdimm_security_ops *cxl_security_ops = &__cxl_security_ops;
> diff --git a/drivers/nvdimm/security.c b/drivers/nvdimm/security.c
> index 8aefb60c42ff..92af4c3ca0d3 100644
> --- a/drivers/nvdimm/security.c
> +++ b/drivers/nvdimm/security.c
> @@ -239,7 +239,8 @@ static int check_security_state(struct nvdimm *nvdimm)
> return 0;
> }
>
> -static int security_disable(struct nvdimm *nvdimm, unsigned int keyid)
> +static int security_disable(struct nvdimm *nvdimm, unsigned int keyid,
> + enum nvdimm_passphrase_type pass_type)
> {
> struct device *dev = &nvdimm->dev;
> struct nvdimm_bus *nvdimm_bus = walk_to_nvdimm_bus(dev);
> @@ -250,8 +251,13 @@ static int security_disable(struct nvdimm *nvdimm, unsigned int keyid)
> /* The bus lock should be held at the top level of the call stack */
> lockdep_assert_held(&nvdimm_bus->reconfig_mutex);
>
> - if (!nvdimm->sec.ops || !nvdimm->sec.ops->disable
> - || !nvdimm->sec.flags)
> + if (!nvdimm->sec.ops || !nvdimm->sec.flags)
> + return -EOPNOTSUPP;
> +
> + if (pass_type == NVDIMM_USER && !nvdimm->sec.ops->disable)
> + return -EOPNOTSUPP;
> +
> + if (pass_type == NVDIMM_MASTER && !nvdimm->sec.ops->disable_master)
> return -EOPNOTSUPP;
>
> rc = check_security_state(nvdimm);
> @@ -263,12 +269,21 @@ static int security_disable(struct nvdimm *nvdimm, unsigned int keyid)
> if (!data)
> return -ENOKEY;
>
> - rc = nvdimm->sec.ops->disable(nvdimm, data);
> - dev_dbg(dev, "key: %d disable: %s\n", key_serial(key),
> + if (pass_type == NVDIMM_MASTER) {
> + rc = nvdimm->sec.ops->disable_master(nvdimm, data);
> + dev_dbg(dev, "key: %d disable_master: %s\n", key_serial(key),
> rc == 0 ? "success" : "fail");
> + } else {
> + rc = nvdimm->sec.ops->disable(nvdimm, data);
> + dev_dbg(dev, "key: %d disable: %s\n", key_serial(key),
> + rc == 0 ? "success" : "fail");
> + }
>
> nvdimm_put_key(key);
> - nvdimm->sec.flags = nvdimm_security_flags(nvdimm, NVDIMM_USER);
> + if (pass_type == NVDIMM_MASTER)
> + nvdimm->sec.ext_flags = nvdimm_security_flags(nvdimm, NVDIMM_MASTER);
> + else
> + nvdimm->sec.flags = nvdimm_security_flags(nvdimm, NVDIMM_USER);
> return rc;
> }
>
> @@ -473,6 +488,7 @@ void nvdimm_security_overwrite_query(struct work_struct *work)
> #define OPS \
> C( OP_FREEZE, "freeze", 1), \
> C( OP_DISABLE, "disable", 2), \
> + C( OP_DISABLE_MASTER, "disable_master", 2), \
> C( OP_UPDATE, "update", 3), \
> C( OP_ERASE, "erase", 2), \
> C( OP_OVERWRITE, "overwrite", 2), \
> @@ -524,7 +540,10 @@ ssize_t nvdimm_security_store(struct device *dev, const char *buf, size_t len)
> rc = nvdimm_security_freeze(nvdimm);
> } else if (i == OP_DISABLE) {
> dev_dbg(dev, "disable %u\n", key);
> - rc = security_disable(nvdimm, key);
> + rc = security_disable(nvdimm, key, NVDIMM_USER);
> + } else if (i == OP_DISABLE_MASTER) {
> + dev_dbg(dev, "disable_master %u\n", key);
> + rc = security_disable(nvdimm, key, NVDIMM_MASTER);
> } else if (i == OP_UPDATE || i == OP_MASTER_UPDATE) {
> dev_dbg(dev, "%s %u %u\n", ops[i].name, key, newkey);
> rc = security_update(nvdimm, key, newkey, i == OP_UPDATE
> diff --git a/include/linux/libnvdimm.h b/include/linux/libnvdimm.h
> index c74acfa1a3fe..3bf658a74ccb 100644
> --- a/include/linux/libnvdimm.h
> +++ b/include/linux/libnvdimm.h
> @@ -183,6 +183,8 @@ struct nvdimm_security_ops {
> int (*overwrite)(struct nvdimm *nvdimm,
> const struct nvdimm_key_data *key_data);
> int (*query_overwrite)(struct nvdimm *nvdimm);
> + int (*disable_master)(struct nvdimm *nvdimm,
> + const struct nvdimm_key_data *key_data);
> };
>
> enum nvdimm_fwa_state {
>
>
next prev parent reply other threads:[~2022-11-14 22:27 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 20:33 [PATCH v4 00/18] Introduce security commands for CXL pmem device Dave Jiang
2022-11-14 20:33 ` [PATCH v4 01/18] cxl/pmem: Introduce nvdimm_security_ops with ->get_flags() operation Dave Jiang
2022-11-14 20:33 ` [PATCH v4 02/18] tools/testing/cxl: Add "Get Security State" opcode support Dave Jiang
2022-11-14 20:33 ` [PATCH v4 03/18] cxl/pmem: Add "Set Passphrase" security command support Dave Jiang
2022-11-14 20:33 ` [PATCH v4 04/18] tools/testing/cxl: Add "Set Passphrase" opcode support Dave Jiang
2022-11-14 20:33 ` [PATCH v4 05/18] cxl/pmem: Add Disable Passphrase security command support Dave Jiang
2022-11-14 20:33 ` [PATCH v4 06/18] tools/testing/cxl: Add "Disable" security opcode support Dave Jiang
2022-11-14 20:33 ` [PATCH v4 07/18] cxl/pmem: Add "Freeze Security State" security command support Dave Jiang
2022-11-14 20:33 ` [PATCH v4 08/18] tools/testing/cxl: Add "Freeze Security State" security opcode support Dave Jiang
2022-11-14 20:33 ` [PATCH v4 09/18] cxl/pmem: Add "Unlock" security command support Dave Jiang
2022-11-14 20:34 ` [PATCH v4 10/18] tools/testing/cxl: Add "Unlock" security opcode support Dave Jiang
2022-11-14 20:34 ` [PATCH v4 11/18] cxl/pmem: Add "Passphrase Secure Erase" security command support Dave Jiang
2022-11-14 20:34 ` [PATCH v4 12/18] tools/testing/cxl: Add "passphrase secure erase" opcode support Dave Jiang
2022-11-15 11:08 ` Jonathan Cameron
2022-11-15 15:57 ` Dave Jiang
2022-11-15 17:01 ` Dave Jiang
2022-11-16 11:43 ` Jonathan Cameron
2022-11-16 21:54 ` Dave Jiang
2022-11-17 11:26 ` Jonathan Cameron
2022-11-16 11:37 ` Jonathan Cameron
2022-11-14 20:34 ` [PATCH v4 13/18] nvdimm/cxl/pmem: Add support for master passphrase disable security command Dave Jiang
2022-11-14 22:27 ` Ben Cheatham [this message]
2022-11-14 22:49 ` Dave Jiang
2022-11-14 20:34 ` [PATCH v4 14/18] cxl/pmem: add id attribute to CXL based nvdimm Dave Jiang
2022-11-14 20:34 ` [PATCH v4 15/18] tools/testing/cxl: add mechanism to lock mem device for testing Dave Jiang
2022-11-14 20:34 ` [PATCH v4 16/18] cxl/pmem: add provider name to cxl pmem dimm attribute group Dave Jiang
2022-11-14 20:34 ` [PATCH v4 17/18] libnvdimm: Introduce CONFIG_NVDIMM_SECURITY_TEST flag Dave Jiang
2022-11-14 20:34 ` [PATCH v4 18/18] cxl: add dimm_id support for __nvdimm_create() 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=1cc14f3f-6500-778a-087c-e7601f82adf3@amd.com \
--to=benjamin.cheatham@amd.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=ira.weiny@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 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.