From: Max Gurtovoy <mgurtovoy@nvidia.com>
To: Christoph Hellwig <hch@lst.de>
Cc: sagi@grimberg.me, kbusch@kernel.org,
linux-nvme@lists.infradead.org, hare@suse.de, axboe@kernel.dk,
oren@nvidia.com, ngottlieb@nvidia.com, israelr@nvidia.com
Subject: Re: [PATCH v2 3/3] nvme-fabrics: prevent overriding of existing host
Date: Fri, 12 May 2023 18:40:14 +0300 [thread overview]
Message-ID: <beef281e-06e9-3dec-63fb-54f188ee483b@nvidia.com> (raw)
In-Reply-To: <20230512145652.GC5051@lst.de>
On 12/05/2023 17:56, Christoph Hellwig wrote:
>> +
>> list_for_each_entry(host, &nvmf_hosts, list) {
>> + if (!strcmp(host->nqn, hostnqn)) {
>> + if (uuid_equal(&host->id, id)) {
>> + // same hostnqn and hostid
>> + return host;
>> + } else {
>> + pr_err("found same hostnqn %s but different hostid %pUb\n",
>> + hostnqn, id);
>> + return ERR_PTR(-EINVAL);
>> + }
>> + } else if (uuid_equal(&host->id, id)) {
>> + // same hostid but different hostnqn
>> + pr_err("found same hostid %pUb but different hostnqn %s\n",
>> + id, hostnqn);
>> + return ERR_PTR(-EINVAL);
>> + }
>> }
>
> Please avoid the c++ style comments. But If the code was structured
> a little different, they might not even be beeded, i.e.
>
> bool same_hostnqn = !strcmp(host->nqn, hostnqn);
> bool same_hostid = uuid_equal(&host->id, id);
>
> if (same_hostnqn && same_hostid)
> return host;
>
> if (same_hostnqn) {
> pr_err("found same hostnqn %s but different hostid %pUb\n",
> hostnqn, id);
> return ERR_PTR(-EINVAL);
> }
> if (same_hostid) {
> pr_err("found same hostid %pUb but different hostnqn %s\n",
> id, hostnqn);
> return ERR_PTR(-EINVAL);
> }
Sure, good idea.
I'll address it in v3.
prev parent reply other threads:[~2023-05-12 15:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 16:54 [PATCH v2 0/3] nvme-fabrics: fix un-expected behaviour related to hostnqn and hostid Max Gurtovoy
2023-05-11 16:54 ` [PATCH v2 1/3] nvme-fabrics: unify common code in admin and io queue connect Max Gurtovoy
2023-05-11 18:44 ` Hannes Reinecke
2023-05-12 14:50 ` Christoph Hellwig
2023-05-11 16:54 ` [PATCH v2 2/3] nvme-fabrics: check hostid using uuid_equal Max Gurtovoy
2023-05-11 18:45 ` Hannes Reinecke
2023-05-12 14:50 ` Christoph Hellwig
2023-05-11 16:54 ` [PATCH v2 3/3] nvme-fabrics: prevent overriding of existing host Max Gurtovoy
2023-05-11 18:50 ` Hannes Reinecke
2023-05-11 19:35 ` Max Gurtovoy
2023-05-11 23:13 ` Hannes Reinecke
2023-05-11 23:20 ` Max Gurtovoy
2023-05-12 14:56 ` Christoph Hellwig
2023-05-12 15:40 ` Max Gurtovoy [this message]
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=beef281e-06e9-3dec-63fb-54f188ee483b@nvidia.com \
--to=mgurtovoy@nvidia.com \
--cc=axboe@kernel.dk \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=israelr@nvidia.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=ngottlieb@nvidia.com \
--cc=oren@nvidia.com \
--cc=sagi@grimberg.me \
/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.