linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jsmart2021@gmail.com (James Smart)
Subject: [PATCH 1/7] nvme: remove unnecessary controller subnqn validation
Date: Mon,  7 May 2018 17:12:08 -0700	[thread overview]
Message-ID: <20180508001214.8951-2-jsmart2021@gmail.com> (raw)
In-Reply-To: <20180508001214.8951-1-jsmart2021@gmail.com>

After creating the nvme controller, nvmf_create_ctrl() validates
the newly created subsysnqn vs the one specified by the options.

In general, this is an unnecessary check as the Connect message
should implicitly ensure this value matches.

With the change to the FC transport to do an asynchronous connect
for the first association create, the transport will return to
nvmf_create_ctrl() before that first association has been established,
thus the subnqn will not yet be set.

Remove the unnecessary validation.

Signed-off-by: James Smart <james.smart at broadcom.com>
---
 drivers/nvme/host/fabrics.c | 10 ----------
 1 file changed, 10 deletions(-)

diff --git a/drivers/nvme/host/fabrics.c b/drivers/nvme/host/fabrics.c
index 7ae732a77fe8..6fdf499d16b4 100644
--- a/drivers/nvme/host/fabrics.c
+++ b/drivers/nvme/host/fabrics.c
@@ -983,16 +983,6 @@ nvmf_create_ctrl(struct device *dev, const char *buf, size_t count)
 		goto out_module_put;
 	}
 
-	if (strcmp(ctrl->subsys->subnqn, opts->subsysnqn)) {
-		dev_warn(ctrl->device,
-			"controller returned incorrect NQN: \"%s\".\n",
-			ctrl->subsys->subnqn);
-		module_put(ops->module);
-		up_read(&nvmf_transports_rwsem);
-		nvme_delete_ctrl_sync(ctrl);
-		return ERR_PTR(-EINVAL);
-	}
-
 	module_put(ops->module);
 	up_read(&nvmf_transports_rwsem);
 	return ctrl;
-- 
2.13.1

  reply	other threads:[~2018-05-08  0:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-08  0:12 [PATCH 0/7] nvme_fc: asynchronous controller create and simple discovery James Smart
2018-05-08  0:12 ` James Smart [this message]
2018-05-08  5:57   ` [PATCH 1/7] nvme: remove unnecessary controller subnqn validation Hannes Reinecke
2018-05-08  0:12 ` [PATCH 2/7] nvme_fc: remove setting DNR on exception conditions James Smart
2018-05-08  5:58   ` Hannes Reinecke
2018-05-08  0:12 ` [PATCH 3/7] nvme_fc: retry failures to set io queue count James Smart
2018-05-08  6:00   ` Hannes Reinecke
2018-05-11 20:19     ` James Smart
2018-05-08  0:12 ` [PATCH 4/7] nvme_fc: remove reinit_request routine James Smart
2018-05-08  6:01   ` Hannes Reinecke
2018-05-08  0:12 ` [PATCH 5/7] nvme_fc: change controllers first connect to use reconnect path James Smart
2018-05-08  6:03   ` Hannes Reinecke
2018-05-08  0:12 ` [PATCH 6/7] nvme_fc: fix nulling of queue data on reconnect James Smart
2018-05-08  6:05   ` Hannes Reinecke
2018-05-08 15:12     ` James Smart
2018-05-08 15:28       ` Hannes Reinecke
2018-05-08  0:12 ` [PATCH 7/7] nvme_fc: add 'nvme_discovery' sysfs attribute to fc transport device James Smart
2018-05-08  6:06   ` Hannes Reinecke

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=20180508001214.8951-2-jsmart2021@gmail.com \
    --to=jsmart2021@gmail.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 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).