All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Dave Jiang <dave.jiang@intel.com>
Cc: <linux-cxl@vger.kernel.org>, <nvdimm@lists.linux.dev>,
	<dan.j.williams@intel.com>, <ira.weiny@intel.com>,
	<vishal.l.verma@intel.com>, <alison.schofield@intel.com>,
	<dave@stgolabs.net>
Subject: Re: [PATCH v7 01/20] cxl/pmem: Introduce nvdimm_security_ops with ->get_flags() operation
Date: Tue, 28 Feb 2023 15:09:11 +0000	[thread overview]
Message-ID: <20230228150911.00002535@Huawei.com> (raw)
In-Reply-To: <166983609611.2734609.13231854299523325319.stgit@djiang5-desk3.ch.intel.com>

On Wed, 30 Nov 2022 12:21:36 -0700
Dave Jiang <dave.jiang@intel.com> wrote:

> Add nvdimm_security_ops support for CXL memory device with the introduction
> of the ->get_flags() callback function. This is part of the "Persistent
> Memory Data-at-rest Security" command set for CXL memory device support.
> The ->get_flags() function provides the security state of the persistent
> memory device defined by the CXL 3.0 spec section 8.2.9.8.6.1.
> 
> Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> Signed-off-by: Dave Jiang <dave.jiang@intel.com>
> Link: https://lore.kernel.org/r/166863346914.80269.2104235260504076729.stgit@djiang5-desk3.ch.intel.com
> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Hi Dave / Dan,

Just looking at build warnings with current upstream with W=1 C=1 and it highlights
and oddity with this patch.


> diff --git a/drivers/cxl/pmem.c b/drivers/cxl/pmem.c
> index 4c627d67281a..efffc731c2ec 100644
> --- a/drivers/cxl/pmem.c
> +++ b/drivers/cxl/pmem.c
> @@ -11,6 +11,8 @@
>  #include "cxlmem.h"
>  #include "cxl.h"
>  
> +extern const struct nvdimm_security_ops *cxl_security_ops;
Why not push this into a header as...
> +
>  /*
>   * Ordered workqueue for cxl nvdimm device arrival and departure
>   * to coordinate bus rescans when a bridge arrives and trigger remove
> @@ -78,8 +80,8 @@ static int cxl_nvdimm_probe(struct device *dev)
>  	set_bit(ND_CMD_GET_CONFIG_SIZE, &cmd_mask);
>  	set_bit(ND_CMD_GET_CONFIG_DATA, &cmd_mask);
>  	set_bit(ND_CMD_SET_CONFIG_DATA, &cmd_mask);
> -	nvdimm = nvdimm_create(cxl_nvb->nvdimm_bus, cxl_nvd, NULL, flags,
> -			       cmd_mask, 0, NULL);
> +	nvdimm = __nvdimm_create(cxl_nvb->nvdimm_bus, cxl_nvd, NULL, flags,
> +				 cmd_mask, 0, NULL, NULL, cxl_security_ops, NULL);
>  	if (!nvdimm) {
>  		rc = -ENOMEM;
>  		goto out;
> diff --git a/drivers/cxl/security.c b/drivers/cxl/security.c
> new file mode 100644
> index 000000000000..806173084216
> --- /dev/null
> +++ b/drivers/cxl/security.c

> +
> +static const struct nvdimm_security_ops __cxl_security_ops = {
> +	.get_flags = cxl_pmem_get_security_flags,
> +};
> +
> +const struct nvdimm_security_ops *cxl_security_ops = &__cxl_security_ops;

otherwise this triggers a should static warning as the compiler can't see the extern
definition.

Jonathan

  reply	other threads:[~2023-02-28 15:09 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-30 19:21 [PATCH v7 00/20] Introduce security commands for CXL pmem device Dave Jiang
2022-11-30 19:21 ` [PATCH v7 01/20] cxl/pmem: Introduce nvdimm_security_ops with ->get_flags() operation Dave Jiang
2023-02-28 15:09   ` Jonathan Cameron [this message]
2023-03-01 23:06     ` [PATCH] cxl: fix compile warning for cxl_security_ops extern Dave Jiang
2023-03-02  0:17       ` Alison Schofield
2023-08-16 18:07         ` Alison Schofield
2023-03-03 12:15       ` Jonathan Cameron
2023-08-04 18:02       ` Alison Schofield
2022-11-30 19:21 ` [PATCH v7 02/20] tools/testing/cxl: Add "Get Security State" opcode support Dave Jiang
2022-11-30 19:21 ` [PATCH v7 03/20] cxl/pmem: Add "Set Passphrase" security command support Dave Jiang
2022-11-30 19:21 ` [PATCH v7 04/20] tools/testing/cxl: Add "Set Passphrase" opcode support Dave Jiang
2022-11-30 19:21 ` [PATCH v7 05/20] cxl/pmem: Add Disable Passphrase security command support Dave Jiang
2022-11-30 19:22 ` [PATCH v7 06/20] tools/testing/cxl: Add "Disable" security opcode support Dave Jiang
2022-11-30 19:22 ` [PATCH v7 07/20] cxl/pmem: Add "Freeze Security State" security command support Dave Jiang
2022-11-30 19:22 ` [PATCH v7 08/20] tools/testing/cxl: Add "Freeze Security State" security opcode support Dave Jiang
2022-11-30 19:22 ` [PATCH v7 09/20] cxl/pmem: Add "Unlock" security command support Dave Jiang
2022-11-30 19:22 ` [PATCH v7 10/20] tools/testing/cxl: Add "Unlock" security opcode support Dave Jiang
2022-11-30 19:22 ` [PATCH v7 11/20] cxl/pmem: Add "Passphrase Secure Erase" security command support Dave Jiang
2022-11-30 19:22 ` [PATCH v7 12/20] tools/testing/cxl: Add "passphrase secure erase" opcode support Dave Jiang
2022-11-30 19:22 ` [PATCH v7 13/20] nvdimm/cxl/pmem: Add support for master passphrase disable security command Dave Jiang
2022-11-30 19:22 ` [PATCH v7 14/20] cxl/pmem: add id attribute to CXL based nvdimm Dave Jiang
2022-11-30 19:22 ` [PATCH v7 15/20] tools/testing/cxl: add mechanism to lock mem device for testing Dave Jiang
2022-11-30 19:23 ` [PATCH v7 16/20] cxl/pmem: add provider name to cxl pmem dimm attribute group Dave Jiang
2022-11-30 19:23 ` [PATCH v7 17/20] libnvdimm: Introduce CONFIG_NVDIMM_SECURITY_TEST flag Dave Jiang
2022-11-30 19:23 ` [PATCH v7 18/20] cxl: bypass cpu_cache_invalidate_memregion() when in test config Dave Jiang
2022-11-30 22:16   ` Davidlohr Bueso
2022-11-30 23:54     ` Dan Williams
2022-12-01  1:51       ` Davidlohr Bueso
2022-12-01  3:05         ` Dan Williams
2022-12-01 11:11   ` Jonathan Cameron
2022-11-30 19:23 ` [PATCH v7 19/20] acpi/nfit: " Dave Jiang
2022-12-01 11:22   ` Jonathan Cameron
2022-11-30 19:23 ` [PATCH v7 20/20] cxl: add dimm_id support for __nvdimm_create() Dave Jiang
2022-12-01  2:20   ` 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=20230228150911.00002535@Huawei.com \
    --to=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.