From: guanjunxiong@huawei.com (Guan Junxiong)
Subject: [PATCH V2] nvme-cli/list: fix when nvme device can not be open
Date: Wed, 2 Aug 2017 15:51:09 +0800 [thread overview]
Message-ID: <1501660269-11024-1-git-send-email-guanjunxiong@huawei.com> (raw)
This patch checks the validity of fd returned by open operation on
the nvme divices. For example, when a user who doesn't have the
permission to open the device trys to use nvme list command to list
nvme devices, the fd is returned as -1 and errno indicates permission
denied.
In addition,this patch closes the current open device before
processing the next device.
Signed-off-by: Guan Junxiong <guanjunxiong at huawei.com>
Reviewed-by: Christoph Hellwig <hch at lst.de>
---
The V1 version was _applied_ in the mail list , but isn't applied into
nvme-cli mainstream. Here comes the new version:
change since V1:
* rebase latest master branch and fix conflicts
* add reviewed-by tag of Christoph
nvme.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/nvme.c b/nvme.c
index 235a1bb..b4a039a 100644
--- a/nvme.c
+++ b/nvme.c
@@ -911,7 +911,13 @@ static int list(int argc, char **argv, struct command *cmd, struct plugin *plugi
for (i = 0; i < n; i++) {
snprintf(path, sizeof(path), "%s%s", dev, devices[i]->d_name);
fd = open(path, O_RDONLY);
+ if (fd < 0) {
+ fprintf(stderr, "can not open %s: %s\n", path,
+ strerror(errno));
+ return errno;
+ }
ret = get_nvme_info(fd, &list_items[i], path);
+ close(fd);
if (ret)
return ret;
}
--
2.11.1
next reply other threads:[~2017-08-02 7:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 7:51 Guan Junxiong [this message]
2017-08-02 8:02 ` [PATCH V2] nvme-cli/list: fix when nvme device can not be open Keith Busch
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=1501660269-11024-1-git-send-email-guanjunxiong@huawei.com \
--to=guanjunxiong@huawei.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