From: Dave Jiang <dave.jiang@intel.com>
To: linux-nvdimm@lists.01.org
Cc: alison.schofield@intel.com, keescook@chromium.org,
ebiggers3@gmail.com, dhowells@redhat.com,
keyrings@vger.kernel.org
Subject: [PATCH v7 08/12] nfit/libnvdimm: add freeze security support to Intel nvdimm
Date: Fri, 03 Aug 2018 17:01:54 -0700 [thread overview]
Message-ID: <153334091448.60955.17393000104848914817.stgit@djiang5-desk3.ch.intel.com> (raw)
In-Reply-To: <153334018216.60955.13349338519981704524.stgit@djiang5-desk3.ch.intel.com>
Add support for freeze security on Intel nvdimm. This locks out any
changes to security for the DIMM unless a reboot is done. This is triggered
by writing "freeze" to the "security" sysfs attribute. libnvdimm will
support the generic freeze_lock API call.
Signed-off-by: Dave Jiang <dave.jiang@intel.com>
Reviewed-by: Dan Williams <dan.j.williams@intel.com>
---
drivers/acpi/nfit/intel.c | 51 ++++++++++++++++++++++++++++++++++++++++++++
drivers/nvdimm/dimm_devs.c | 22 +++++++++++++++++++
include/linux/libnvdimm.h | 2 ++
3 files changed, 75 insertions(+)
diff --git a/drivers/acpi/nfit/intel.c b/drivers/acpi/nfit/intel.c
index 21d30222371f..ba886f1f5399 100644
--- a/drivers/acpi/nfit/intel.c
+++ b/drivers/acpi/nfit/intel.c
@@ -18,6 +18,53 @@
#include "intel.h"
#include "nfit.h"
+static int intel_dimm_security_freeze_lock(struct nvdimm_bus *nvdimm_bus,
+ struct nvdimm *nvdimm)
+{
+ struct nvdimm_bus_descriptor *nd_desc = to_nd_desc(nvdimm_bus);
+ int cmd_rc, rc = 0;
+ struct nfit_mem *nfit_mem = nvdimm_provider_data(nvdimm);
+ struct {
+ struct nd_cmd_pkg pkg;
+ struct nd_intel_freeze_lock cmd;
+ } nd_cmd = {
+ .pkg = {
+ .nd_command = NVDIMM_INTEL_FREEZE_LOCK,
+ .nd_family = NVDIMM_FAMILY_INTEL,
+ .nd_size_in = 0,
+ .nd_size_out = ND_INTEL_STATUS_SIZE,
+ .nd_fw_size = ND_INTEL_STATUS_SIZE,
+ },
+ .cmd = {
+ .status = 0,
+ },
+ };
+
+ if (!test_bit(NVDIMM_INTEL_FREEZE_LOCK, &nfit_mem->dsm_mask))
+ return -ENOTTY;
+
+ rc = nd_desc->ndctl(nd_desc, nvdimm, ND_CMD_CALL, &nd_cmd,
+ sizeof(nd_cmd), &cmd_rc);
+ if (rc < 0)
+ goto out;
+ if (cmd_rc < 0) {
+ rc = cmd_rc;
+ goto out;
+ }
+
+ switch (nd_cmd.cmd.status) {
+ case 0:
+ break;
+ case ND_INTEL_STATUS_INVALID_STATE:
+ default:
+ rc = -ENXIO;
+ goto out;
+ }
+
+ out:
+ return rc;
+}
+
static int intel_dimm_security_disable(struct nvdimm_bus *nvdimm_bus,
struct nvdimm *nvdimm, const struct nvdimm_key_data *nkey)
{
@@ -254,6 +301,9 @@ static int intel_dimm_security_state(struct nvdimm_bus *nvdimm_bus,
else if (nd_cmd.cmd.state & ND_INTEL_SEC_STATE_ENABLED) {
if (nd_cmd.cmd.state & ND_INTEL_SEC_STATE_LOCKED)
*state = NVDIMM_SECURITY_LOCKED;
+ else if (nd_cmd.cmd.state & ND_INTEL_SEC_STATE_FROZEN ||
+ nd_cmd.cmd.state & ND_INTEL_SEC_STATE_PLIMIT)
+ *state = NVDIMM_SECURITY_FROZEN;
else
*state = NVDIMM_SECURITY_UNLOCKED;
} else
@@ -270,4 +320,5 @@ const struct nvdimm_security_ops intel_security_ops = {
.unlock = intel_dimm_security_unlock,
.change_key = intel_dimm_security_update_passphrase,
.disable = intel_dimm_security_disable,
+ .freeze_lock = intel_dimm_security_freeze_lock,
};
diff --git a/drivers/nvdimm/dimm_devs.c b/drivers/nvdimm/dimm_devs.c
index 4169aabe814e..ccb5fd13cd57 100644
--- a/drivers/nvdimm/dimm_devs.c
+++ b/drivers/nvdimm/dimm_devs.c
@@ -143,6 +143,26 @@ int nvdimm_security_get_state(struct device *dev)
&nvdimm->state);
}
+static int nvdimm_security_freeze_lock(struct device *dev)
+{
+ struct nvdimm *nvdimm = to_nvdimm(dev);
+ struct nvdimm_bus *nvdimm_bus = walk_to_nvdimm_bus(dev);
+ int rc;
+
+ if (!nvdimm->security_ops)
+ return 0;
+
+ if (nvdimm->state == NVDIMM_SECURITY_UNSUPPORTED)
+ return 0;
+
+ rc = nvdimm->security_ops->freeze_lock(nvdimm_bus, nvdimm);
+ if (rc < 0)
+ return rc;
+
+ nvdimm_security_get_state(dev);
+ return 0;
+}
+
static int nvdimm_security_disable(struct device *dev)
{
struct nvdimm *nvdimm = to_nvdimm(dev);
@@ -795,6 +815,8 @@ static ssize_t security_store(struct device *dev,
rc = nvdimm_security_change_key(dev, old_id, new_id);
} else if (sysfs_streq(buf, "disable"))
rc = nvdimm_security_disable(dev);
+ else if (sysfs_streq(buf, "freeze"))
+ rc = nvdimm_security_freeze_lock(dev);
else
return -EINVAL;
diff --git a/include/linux/libnvdimm.h b/include/linux/libnvdimm.h
index c60ab4b238f3..bcab42caa948 100644
--- a/include/linux/libnvdimm.h
+++ b/include/linux/libnvdimm.h
@@ -185,6 +185,8 @@ struct nvdimm_security_ops {
int (*disable)(struct nvdimm_bus *nvdimm_bus,
struct nvdimm *nvdimm,
const struct nvdimm_key_data *nkey);
+ int (*freeze_lock)(struct nvdimm_bus *nvdimm_bus,
+ struct nvdimm *nvdimm);
};
void badrange_init(struct badrange *badrange);
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
next prev parent reply other threads:[~2018-08-04 0:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-04 0:01 [PATCH v7 00/12] Adding security support for nvdimm Dave Jiang
2018-08-04 0:01 ` [PATCH v7 01/12] nfit: add support for Intel DSM 1.7 commands Dave Jiang
2018-08-04 0:01 ` [PATCH v7 02/12] libnvdimm: create keyring to store security keys Dave Jiang
2018-08-04 0:01 ` [PATCH v7 03/12] nfit/libnvdimm: store dimm id as a member to struct nvdimm Dave Jiang
2018-08-04 0:01 ` [PATCH v7 04/12] keys: export lookup_user_key to external users Dave Jiang
2018-08-04 0:01 ` [PATCH v7 05/12] nfit/libnvdimm: add unlock of nvdimm support for Intel DIMMs Dave Jiang
2018-08-04 0:01 ` [PATCH v7 06/12] nfit/libnvdimm: add set passphrase support for Intel nvdimms Dave Jiang
2018-08-04 0:01 ` [PATCH v7 07/12] nfit/libnvdimm: add disable passphrase support to Intel nvdimm Dave Jiang
2018-08-04 0:01 ` Dave Jiang [this message]
2018-08-04 0:02 ` [PATCH v7 09/12] nfit/libnvdimm: add support for issue secure erase DSM " Dave Jiang
2018-08-04 0:02 ` [PATCH v7 10/12] nfit_test: add context to dimm_dev for nfit_test Dave Jiang
2018-08-04 0:02 ` [PATCH v7 11/12] nfit_test: add test support for Intel nvdimm security DSMs Dave Jiang
2018-08-04 0:02 ` [PATCH v7 12/12] libnvdimm: add documentation for nvdimm security support 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=153334091448.60955.17393000104848914817.stgit@djiang5-desk3.ch.intel.com \
--to=dave.jiang@intel.com \
--cc=alison.schofield@intel.com \
--cc=dhowells@redhat.com \
--cc=ebiggers3@gmail.com \
--cc=keescook@chromium.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-nvdimm@lists.01.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;
as well as URLs for NNTP newsgroup(s).