From: james_p_freyensee@linux.intel.com (Jay Freyensee)
Subject: [PATCH] nvme-cli: user-defined hostnqn option for discover
Date: Thu, 28 Jul 2016 13:03:20 -0700 [thread overview]
Message-ID: <1469736200-6618-2-git-send-email-james_p_freyensee@linux.intel.com> (raw)
In-Reply-To: <1469736200-6618-1-git-send-email-james_p_freyensee@linux.intel.com>
The nvme-cli will always use the default hostnqn
in /dev/nvme-fabrics for the discovery query, even though
both the NVMe Target and NVMe Host rdma implementations allow
user-defined hostnqn naming.
For example, this is the current, somewhat broken behavior if you
used your own hostnqn provision naming on the NVMe kernel target:
nvme discover /dev/nvme-fabrics -t rdma --traddr=192.168.1.3 --trsvcid=4420
in dmesg:
[591910.025779] nvme nvme0: Connect Invalid Data Parameter, hostnqn "nqn.2014-08.org.nvmexpress:NVMf:uuid:a2d7752c-a31b-477a-a003-31a5e1c424a9"
New, fixed behavior introduced by this patch:
[root at fedora23-fabrics-host1 nvme-cli]# nvme discover -t rdma --traddr=192.168.1.3 --trsvcid=4420 --hostnqn=host1-rogue-nqn
Discovery Log Number of Records 1, Generation counter 10
=====Discovery Log Entry 0======
trtype: ipv4
adrfam: rdma
nqntype: 2
treq: 0
portid: 1
trsvcid: 4420
subnqn: nullside-nqn
traddr: 192.168.1.3
rdma_prtype: 0
rdma_qptype: 0
rdma_cms: 0
rdma_pkey: 0x0000
[root at fedora23-fabrics-host1 nvme-cli]#
Signed-off-by: Jay Freyensee <james_p_freyensee at linux.intel.com>
---
fabrics.c | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/fabrics.c b/fabrics.c
index 3666a01..41a80df 100644
--- a/fabrics.c
+++ b/fabrics.c
@@ -49,6 +49,7 @@ struct config {
char *transport;
char *traddr;
char *trsvcid;
+ char *hostnqn;
char *raw;
char *device;
} cfg = { 0 };
@@ -395,6 +396,14 @@ static int build_options(char *argstr, int max_len)
max_len -= len;
}
+ if (cfg.hostnqn) {
+ len = snprintf(argstr, max_len, ",hostnqn=%s", cfg.hostnqn);
+ if (len < 0)
+ return -EINVAL;
+ argstr += len;
+ max_len -= len;
+ }
+
return 0;
}
@@ -525,6 +534,8 @@ int discover(const char *desc, int argc, char **argv, bool connect)
"transport address" },
{"trsvcid", 's', "LIST", CFG_STRING, &cfg.trsvcid, required_argument,
"transport service id (e.g. IP port)" },
+ {"hostnqn", 'h', "LIST", CFG_STRING, &cfg.hostnqn, required_argument,
+ "user-defined hostnqn (if default not used)" },
{"raw", 'r', "LIST", CFG_STRING, &cfg.raw, required_argument,
"raw output file" },
{0},
--
2.4.3
next prev parent reply other threads:[~2016-07-28 20:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 20:03 [PATCH] *** Discovery feature fix in nvme-cli *** Jay Freyensee
2016-07-28 20:03 ` Jay Freyensee [this message]
2016-07-28 20:20 ` [PATCH] nvme-cli: user-defined hostnqn option for discover Roy Shterman
2016-07-28 20:35 ` Keith Busch
2016-07-28 21:21 ` J Freyensee
[not found] ` <45CF57A8-206F-4353-9386-A0BB8158AB5A@mellanox.com>
2016-07-28 21:36 ` [PATCH] [RESEND] " J Freyensee
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=1469736200-6618-2-git-send-email-james_p_freyensee@linux.intel.com \
--to=james_p_freyensee@linux.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 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).