From: Dan Williams <dan.j.williams@intel.com>
To: Dave Jiang <dave.jiang@intel.com>
Cc: David Howells <dhowells@redhat.com>,
"Schofield, Alison <alison.schofield@intel.com>,
keyrings@vger.kernel.org, Kees Cook" <keescook@chromium.org>,
linux-nvdimm <linux-nvdimm@lists.01.org>
Subject: Re: [PATCH v4 03/11] nfit/libnvdimm: store dimm id as a member to struct nvdimm
Date: Fri, 13 Jul 2018 16:17:37 -0700 [thread overview]
Message-ID: <CAPcyv4jq_8oJTAKxrxmwR36OzOiiiWrgxzMBvctCgDhmTJrqSA@mail.gmail.com> (raw)
In-Reply-To: <153142852403.27297.4482491306340625013.stgit@djiang5-desk3.ch.intel.com>
On Thu, Jul 12, 2018 at 1:48 PM, Dave Jiang <dave.jiang@intel.com> wrote:
> The generated dimm id is needed for the sysfs attribute as well as being
> used as the identifier/description for the security key. Since it's
> constant and should never change, store it as a member of struct nvdimm.
>
> Signed-off-by: Dave Jiang <dave.jiang@intel.com>
> ---
> drivers/acpi/nfit/core.c | 35 +++++++++++++++++++++++------------
> drivers/acpi/nfit/nfit.h | 1 +
> drivers/nvdimm/dimm_devs.c | 4 +++-
> drivers/nvdimm/nd-core.h | 1 +
> include/linux/libnvdimm.h | 2 +-
> 5 files changed, 29 insertions(+), 14 deletions(-)
>
> diff --git a/drivers/acpi/nfit/core.c b/drivers/acpi/nfit/core.c
> index a3a944751e6a..dcb5f428bd9c 100644
> --- a/drivers/acpi/nfit/core.c
> +++ b/drivers/acpi/nfit/core.c
> @@ -71,6 +71,9 @@ struct nfit_table_prev {
>
> static guid_t nfit_uuid[NFIT_UUID_MAX];
>
> +static int acpi_nfit_get_dimm_id(struct acpi_nfit_control_region *dcr,
> + char *buf);
> +
> const guid_t *to_nfit_uuid(enum nfit_uuids id)
> {
> return &nfit_uuid[id];
> @@ -1572,18 +1575,10 @@ static DEVICE_ATTR_RO(flags);
> static ssize_t id_show(struct device *dev,
> struct device_attribute *attr, char *buf)
> {
> - struct acpi_nfit_control_region *dcr = to_nfit_dcr(dev);
> + struct nvdimm *nvdimm = to_nvdimm(dev);
> + struct nfit_mem *nfit_mem = nvdimm_provider_data(nvdimm);
>
> - if (dcr->valid_fields & ACPI_NFIT_CONTROL_MFG_INFO_VALID)
> - return sprintf(buf, "%04x-%02x-%04x-%08x\n",
> - be16_to_cpu(dcr->vendor_id),
> - dcr->manufacturing_location,
> - be16_to_cpu(dcr->manufacturing_date),
> - be32_to_cpu(dcr->serial_number));
> - else
> - return sprintf(buf, "%04x-%08x\n",
> - be16_to_cpu(dcr->vendor_id),
> - be32_to_cpu(dcr->serial_number));
> + return sprintf(buf, "%s\n", nfit_mem->id);
> }
> static DEVICE_ATTR_RO(id);
>
> @@ -1830,6 +1825,21 @@ static void shutdown_dimm_notify(void *data)
> mutex_unlock(&acpi_desc->init_mutex);
> }
>
> +static int acpi_nfit_get_dimm_id(struct acpi_nfit_control_region *dcr,
> + char *buf)
> +{
> + if (dcr->valid_fields & ACPI_NFIT_CONTROL_MFG_INFO_VALID)
> + return sprintf(buf, "%04x-%02x-%04x-%08x",
> + be16_to_cpu(dcr->vendor_id),
> + dcr->manufacturing_location,
> + be16_to_cpu(dcr->manufacturing_date),
> + be32_to_cpu(dcr->serial_number));
> + else
> + return sprintf(buf, "%04x-%08x",
> + be16_to_cpu(dcr->vendor_id),
> + be32_to_cpu(dcr->serial_number));
> +}
> +
> static int acpi_nfit_register_dimms(struct acpi_nfit_desc *acpi_desc)
> {
> struct nfit_mem *nfit_mem;
> @@ -1896,10 +1906,11 @@ static int acpi_nfit_register_dimms(struct acpi_nfit_desc *acpi_desc)
>
> flush = nfit_mem->nfit_flush ? nfit_mem->nfit_flush->flush
> : NULL;
> + acpi_nfit_get_dimm_id(nfit_mem->dcr, nfit_mem->id);
It feels odd to initialize this late right before the dimm is
registered with the bus when the rest of the nfit_mem initialization
happens in acpi_nfit_add_dimm(). I think we can just open code
acpi_nfit_get_dimm_id() inside acpi_nfit_add_dimm() and call it done.
> nvdimm = nvdimm_create(acpi_desc->nvdimm_bus, nfit_mem,
> acpi_nfit_dimm_attribute_groups,
> flags, cmd_mask, flush ? flush->hint_count : 0,
> - nfit_mem->flush_wpq);
> + nfit_mem->flush_wpq, nfit_mem->id);
> if (!nvdimm)
> return -ENOMEM;
>
> diff --git a/drivers/acpi/nfit/nfit.h b/drivers/acpi/nfit/nfit.h
> index 40b0003b1805..019549138133 100644
> --- a/drivers/acpi/nfit/nfit.h
> +++ b/drivers/acpi/nfit/nfit.h
> @@ -195,6 +195,7 @@ struct nfit_mem {
> int family;
> bool has_lsr;
> bool has_lsw;
> + char id[NVDIMM_KEY_DESC_LEN];
I think this length should be something like NFIT_DIMM_ID_LEN since it
is independent of the key stuff, it's just the NFIT id that *happens*
to also be used to generate the key id.
> };
>
> struct acpi_nfit_desc {
> diff --git a/drivers/nvdimm/dimm_devs.c b/drivers/nvdimm/dimm_devs.c
> index 1dcbb653455b..1842c74413fa 100644
> --- a/drivers/nvdimm/dimm_devs.c
> +++ b/drivers/nvdimm/dimm_devs.c
> @@ -440,7 +440,7 @@ EXPORT_SYMBOL_GPL(nvdimm_attribute_group);
> struct nvdimm *nvdimm_create(struct nvdimm_bus *nvdimm_bus, void *provider_data,
> const struct attribute_group **groups, unsigned long flags,
> unsigned long cmd_mask, int num_flush,
> - struct resource *flush_wpq)
> + struct resource *flush_wpq, const char *id)
> {
> struct nvdimm *nvdimm = kzalloc(sizeof(*nvdimm), GFP_KERNEL);
> struct device *dev;
> @@ -453,6 +453,8 @@ struct nvdimm *nvdimm_create(struct nvdimm_bus *nvdimm_bus, void *provider_data,
> kfree(nvdimm);
> return NULL;
> }
> +
> + memcpy(nvdimm->dimm_id, id, NVDIMM_KEY_DESC_LEN);
> nvdimm->provider_data = provider_data;
> nvdimm->flags = flags;
> nvdimm->cmd_mask = cmd_mask;
> diff --git a/drivers/nvdimm/nd-core.h b/drivers/nvdimm/nd-core.h
> index 2af0f89c4010..ea9227498dac 100644
> --- a/drivers/nvdimm/nd-core.h
> +++ b/drivers/nvdimm/nd-core.h
> @@ -42,6 +42,7 @@ struct nvdimm {
> atomic_t busy;
> int id, num_flush;
> struct resource *flush_wpq;
> + char dimm_id[NVDIMM_KEY_DESC_LEN];
Hmm, I don't think struct nvdimm needs it's own storage for dimm_id.
Just make this a pointer and assign it the passed in value. It's
guaranteed that the nfit_mem object will stay around as long as the
nvdimm is registered.
With those minor fixups you can add:
Reviewed-by: Dan Williams <dan.j.williams@intel.com>
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
next prev parent reply other threads:[~2018-07-13 23:17 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-12 20:48 [PATCH v4 00/11] Adding security support for nvdimm Dave Jiang
2018-07-12 20:48 ` [PATCH v4 01/11] nfit: add support for Intel DSM 1.7 commands Dave Jiang
2018-07-13 23:04 ` Dan Williams
2018-07-12 20:48 ` [PATCH v4 02/11] libnvdimm: create keyring to store security keys Dave Jiang
2018-07-13 23:05 ` Dan Williams
2018-07-12 20:48 ` [PATCH v4 03/11] nfit/libnvdimm: store dimm id as a member to struct nvdimm Dave Jiang
2018-07-13 23:17 ` Dan Williams [this message]
2018-07-12 20:48 ` [PATCH v4 04/11] nfit/libnvdimm: add unlock of nvdimm support for Intel DIMMs Dave Jiang
2018-07-13 23:19 ` Dan Williams
2018-07-12 20:48 ` [PATCH v4 05/11] nfit/libnvdimm: add set passphrase support for Intel nvdimms Dave Jiang
2018-07-13 23:26 ` Dan Williams
2018-07-16 21:59 ` Dave Jiang
2018-07-16 22:12 ` Dan Williams
2018-07-12 20:49 ` [PATCH v4 06/11] nfit/libnvdimm: add disable passphrase support to Intel nvdimm Dave Jiang
2018-07-13 23:29 ` Dan Williams
2018-07-12 20:49 ` [PATCH v4 07/11] nfit/libnvdimm: add freeze security " Dave Jiang
2018-07-13 23:34 ` Dan Williams
2018-07-12 20:49 ` [PATCH v4 08/11] nfit/libnvdimm: add support for issue secure erase DSM " Dave Jiang
2018-07-13 23:42 ` Dan Williams
2018-07-12 20:49 ` [PATCH v4 09/11] nfit_test: add context to dimm_dev for nfit_test Dave Jiang
2018-07-13 23:54 ` Dan Williams
2018-07-12 20:49 ` [PATCH v4 10/11] nfit_test: add test support for Intel nvdimm security DSMs Dave Jiang
2018-07-13 23:55 ` Dan Williams
2018-07-12 20:49 ` [PATCH v4 11/11] libnvdimm: add documentation for nvdimm security support Dave Jiang
2018-07-14 0:01 ` Dan Williams
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=CAPcyv4jq_8oJTAKxrxmwR36OzOiiiWrgxzMBvctCgDhmTJrqSA@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dhowells@redhat.com \
--cc=keescook@chromium.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).