From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Hannes Reinecke <hare@kernel.org>
Cc: Sagi Grimberg <sagi@grimberg.me>, Christoph Hellwig <hch@lst.de>,
Keith Busch <kbusch@kernel.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
Hannes Reinecke <hare@suse.de>
Subject: Re: [PATCHv4] nvmet: implement unique discovery NQN
Date: Fri, 22 Mar 2024 09:43:41 +0000 [thread overview]
Message-ID: <dc120432-e759-44bb-8667-78e381be61ee@nvidia.com> (raw)
In-Reply-To: <20240322070927.30454-1-hare@kernel.org>
On 3/22/2024 12:09 AM, Hannes Reinecke wrote:
> From: Hannes Reinecke <hare@suse.de>
>
> Unique discovery NQNs allow to differentiate between discovery
> services from (typically physically separate) NVMe-oF subsystems.
> This is required for establishing secured connections as otherwise
> the credentials won't be unique and the integrity of the connection
> cannot be guaranteed.
> This patch adda a configfs attribute 'discovery_nqn' in the 'nvmet'
> configfs directory to specify the unique discovery NQN.
>
> Signed-off-by: Hannes Reinecke <hare@suse.de>
> ---
umm change log ?
> drivers/nvme/target/configfs.c | 46 ++++++++++++++++++++++++++++++++++
> drivers/nvme/target/core.c | 7 ++++++
> 2 files changed, 53 insertions(+)
>
> diff --git a/drivers/nvme/target/configfs.c b/drivers/nvme/target/configfs.c
> index 77a6e817b315..e8ead4ab35aa 100644
> --- a/drivers/nvme/target/configfs.c
> +++ b/drivers/nvme/target/configfs.c
> @@ -1613,6 +1613,11 @@ static struct config_group *nvmet_subsys_make(struct config_group *group,
> return ERR_PTR(-EINVAL);
> }
>
> + if (sysfs_streq(name, nvmet_disc_subsys->subsysnqn)) {
> + pr_err("can't create subsystem using unique discovery NQN\n");
> + return ERR_PTR(-EINVAL);
> + }
> +
> subsys = nvmet_subsys_alloc(name, NVME_NQN_NVME);
> if (IS_ERR(subsys))
> return ERR_CAST(subsys);
> @@ -2159,7 +2164,48 @@ static const struct config_item_type nvmet_hosts_type = {
>
> static struct config_group nvmet_hosts_group;
>
> +static ssize_t nvmet_root_discovery_nqn_show(struct config_item *item,
> + char *page)
> +{
> + return sprintf(page, "%s\n", nvmet_disc_subsys->subsysnqn);
> +}
> +
snprintf() with PAGE_SIZE ?
> +static ssize_t nvmet_root_discovery_nqn_store(struct config_item *item,
> + const char *page, size_t count)
> +{
> + struct list_head *entry;
> + size_t len;
> +
> + len = strcspn(page, "\n");
> + if (!len || len > NVMF_NQN_FIELD_LEN - 1)
> + return -EINVAL;
> +
> + down_write(&nvmet_config_sem);
> + list_for_each(entry, &nvmet_subsystems_group.cg_children) {
> + struct config_item *item =
> + container_of(entry, struct config_item, ci_entry);
newline here ?
> + if (!strncmp(config_item_name(item), page, len)) {
> + pr_err("duplicate NQN %s\n", config_item_name(item));
> + up_write(&nvmet_config_sem);
> + return -EINVAL;
> + }
> + }
> + memset(nvmet_disc_subsys->subsysnqn, 0, NVMF_NQN_FIELD_LEN);
> + memcpy(nvmet_disc_subsys->subsysnqn, page, len);
> + up_write(&nvmet_config_sem);
> +
> + return len;
> +}
-ck
next prev parent reply other threads:[~2024-03-22 9:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 7:09 [PATCHv4] nvmet: implement unique discovery NQN Hannes Reinecke
2024-03-22 9:43 ` Chaitanya Kulkarni [this message]
2024-03-22 9:57 ` Hannes Reinecke
2024-03-23 20:32 ` Sagi Grimberg
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=dc120432-e759-44bb-8667-78e381be61ee@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=hare@kernel.org \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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