From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH nvme-cli] nvme-cli: add ns-descs subcommand
Date: Tue, 20 Jun 2017 02:29:17 -0700 [thread overview]
Message-ID: <20170620092917.GA17947@infradead.org> (raw)
In-Reply-To: <20170620092028.5083-1-jthumshirn@suse.de>
> +int nvme_identify_ns_descs(int fd, __u32 nsid, void *data)
> +{
> +
> + return nvme_identify(fd, nsid, 0x3, data);
> +}
This should use NVME_ID_CNS_NS_DESC_LIST. nvme-cli doesn't currently
have that, but that's just a sign it needs a resync with the kernel
nvme.h.
Also personally I find the nvme_identify_* wrappers rather pointless,
and thin kthey should be removed instead of adding more.
> diff --git a/nvme-print.c b/nvme-print.c
> index 2da5acd5c9b8..582d15a7c5e8 100644
> --- a/nvme-print.c
> +++ b/nvme-print.c
> @@ -3,6 +3,8 @@
> #include <string.h>
> #include <stdlib.h>
>
> +#include <uuid/uuid.h>
libuuid usage in nvme-cli is conditional on LIBUUID. Not that I
particularly agree on stubbing this depdency out..
> +enum {
> + NVME_NIDT_EUI64 = 0x1,
> + NVME_NIDT_NGUID = 0x2,
> + NVME_NIDT_UUID = 0x3,
> +};
Should use values from the updated nvme.h:
> + struct nvme_ns_id_desc {
> + __u8 nidt;
> + __u8 nidl;
> + __u16 reserved;
> + };
Same here.
> + for (pos = 0; pos < 0x1000; pos += len) {
Same here for the magic constant.
> + switch (cur->nidt) {
> + case NVME_NIDT_EUI64:
> + memset(eui64, 0, sizeof(eui64_str));
> + memcpy(eui64_desc, data + off, sizeof(eui64_desc));
What's the point of this memcpy? Alignment?
next prev parent reply other threads:[~2017-06-20 9:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 9:20 [PATCH nvme-cli] nvme-cli: add ns-descs subcommand Johannes Thumshirn
2017-06-20 9:29 ` Christoph Hellwig [this message]
2017-06-20 9:33 ` Johannes Thumshirn
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=20170620092917.GA17947@infradead.org \
--to=hch@infradead.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 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.