From: mgandhi@redhat.com (Milan P. Gandhi)
Subject: [PATCH] Remove extra goto label from nvmet_ns_enable
Date: Thu, 9 Aug 2018 19:03:44 +0530 [thread overview]
Message-ID: <20180809133344.GA11707@machine1> (raw)
Currently nvmet_ns_enable has two labels viz. out_unlock and
out_dev_put, and the reverse call from out_dev_put to out_unlock
is little bit confusing. We could simplify it by calling
nvmet_ns_dev_disable before. This would eliminate need for
2nd label out_dev_put.
Also, this function already initializes ret variable to 0,
so there is no need to initialize it to 0 before out_unlock,
so removing it.
Signed-off-by: Milan P. Gandhi <mgandhi at redhat.com>
---
drivers/nvme/target/core.c | 12 +++++-------
1 file changed, 5 insertions(+), 7 deletions(-)
diff --git a/drivers/nvme/target/core.c b/drivers/nvme/target/core.c
index 9838103f2d62..b40fb6d724b4 100644
--- a/drivers/nvme/target/core.c
+++ b/drivers/nvme/target/core.c
@@ -346,9 +346,10 @@ int nvmet_ns_enable(struct nvmet_ns *ns)
ret = percpu_ref_init(&ns->ref, nvmet_destroy_namespace,
0, GFP_KERNEL);
- if (ret)
- goto out_dev_put;
-
+ if (ret) {
+ nvmet_ns_dev_disable(ns);
+ goto out_unlock;
+ }
if (ns->nsid > subsys->max_nsid)
subsys->max_nsid = ns->nsid;
@@ -372,13 +373,10 @@ int nvmet_ns_enable(struct nvmet_ns *ns)
nvmet_ns_changed(subsys, ns->nsid);
ns->enabled = true;
- ret = 0;
+
out_unlock:
mutex_unlock(&subsys->lock);
return ret;
-out_dev_put:
- nvmet_ns_dev_disable(ns);
- goto out_unlock;
}
void nvmet_ns_disable(struct nvmet_ns *ns)
--
2.14.3
next reply other threads:[~2018-08-09 13:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-09 13:33 Milan P. Gandhi [this message]
[not found] ` <CAMNNMLFyLwk1n2_WTzqEhTJ=U+qseoFKe0=BV94aDZDekVrmuA@mail.gmail.com>
2018-08-09 14:03 ` [PATCH] Remove extra goto label from nvmet_ns_enable Milan P. Gandhi
2018-08-22 13:00 ` Christoph Hellwig
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=20180809133344.GA11707@machine1 \
--to=mgandhi@redhat.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).