public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Busch <keith.busch@intel.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Jens Axboe <axboe@kernel.dk>, Sagi Grimberg <sagi@grimberg.me>,
	linux-nvme@lists.infradead.org, linux-block@vger.kernel.org
Subject: Re: [PATCH 06/10] nvme: track subsystems
Date: Wed, 23 Aug 2017 18:04:34 -0400	[thread overview]
Message-ID: <20170823220434.GB16596@localhost.localdomain> (raw)
In-Reply-To: <20170823175815.3646-7-hch@lst.de>

Looks great. A few minor comments below.

On Wed, Aug 23, 2017 at 07:58:11PM +0200, Christoph Hellwig wrote:
> +static struct nvme_subsystem *__nvme_find_get_subsystem(const char *subsysnqn)
> +{
> +	struct nvme_subsystem *subsys;
> +
> +	lockdep_assert_held(&nvme_subsystems_lock);
> +
> +	list_for_each_entry(subsys, &nvme_subsystems, entry) {
> +		if (strcmp(subsys->subnqn, subsysnqn))
> +			continue;
> +		if (!kref_get_unless_zero(&subsys->ref))
> +			continue;

You should be able to just return immediately here since there can't be
a duplicated subsysnqn in the list.

> +		return subsys;
> +	}
> +
> +	return NULL;
> +}
> +
> +static int nvme_init_subsystem(struct nvme_ctrl *ctrl, struct nvme_id_ctrl *id)
> +{
> +	struct nvme_subsystem *subsys, *found;
> +
> +	subsys = kzalloc(sizeof(*subsys), GFP_KERNEL);
> +	if (!subsys)
> +		return -ENOMEM;
> +	INIT_LIST_HEAD(&subsys->ctrls);
> +	kref_init(&subsys->ref);
> +	nvme_init_subnqn(subsys, ctrl, id);
> +	mutex_init(&subsys->lock);
> +
> +	mutex_lock(&nvme_subsystems_lock);

This could be a spinlock instead of a mutex.

> +	found = __nvme_find_get_subsystem(subsys->subnqn);
> +	if (found) {
> +		/*
> +		 * Verify that the subsystem actually supports multiple
> +		 * controllers, else bail out.
> +		 */
> +		kfree(subsys);
> +		if (!(id->cmic & (1 << 1))) {
> +			dev_err(ctrl->device,
> +				"ignoring ctrl due to duplicate subnqn (%s).\n",
> +				found->subnqn);
> +			mutex_unlock(&nvme_subsystems_lock);
> +			return -EINVAL;

Returning -EINVAL here will cause nvme_init_identify to fail. Do we want
that to happen here? I think we want to be able to manage controllers
in such a state, but just checking if there's a good reason to not allow
them.

> +		}
> +
> +		subsys = found;
> +	} else {
> +		list_add_tail(&subsys->entry, &nvme_subsystems);
> +	}
> +
> +	ctrl->subsys = subsys;
> +	mutex_unlock(&nvme_subsystems_lock);
> +
> +	mutex_lock(&subsys->lock);
> +	list_add_tail(&ctrl->subsys_entry, &subsys->ctrls);
> +	mutex_unlock(&subsys->lock);
> +
> +	return 0;
>  }
>  
>  /*
> @@ -1801,7 +1882,11 @@ int nvme_init_identify(struct nvme_ctrl *ctrl)
>  		return -EIO;
>  	}
>  
> -	nvme_init_subnqn(ctrl, id);
> +	ret = nvme_init_subsystem(ctrl, id);
> +	if (ret) {
> +		kfree(id);
> +		return ret;
> +	}

  reply	other threads:[~2017-08-23 22:04 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-23 17:58 RFC: nvme multipath support Christoph Hellwig
2017-08-23 17:58 ` [PATCH 01/10] nvme: report more detailed status codes to the block layer Christoph Hellwig
2017-08-28  6:06   ` Sagi Grimberg
2017-08-28 18:50   ` Keith Busch
2017-08-23 17:58 ` [PATCH 02/10] nvme: allow calling nvme_change_ctrl_state from irq context Christoph Hellwig
2017-08-28  6:06   ` Sagi Grimberg
2017-08-28 18:50   ` Keith Busch
2017-08-23 17:58 ` [PATCH 03/10] nvme: remove unused struct nvme_ns fields Christoph Hellwig
2017-08-28  6:07   ` Sagi Grimberg
2017-08-28 19:13   ` Keith Busch
2017-08-23 17:58 ` [PATCH 04/10] nvme: remove nvme_revalidate_ns Christoph Hellwig
2017-08-28  6:12   ` Sagi Grimberg
2017-08-28 19:14   ` Keith Busch
2017-08-23 17:58 ` [PATCH 05/10] nvme: don't blindly overwrite identifiers on disk revalidate Christoph Hellwig
2017-08-28  6:17   ` Sagi Grimberg
2017-08-28  6:23     ` Christoph Hellwig
2017-08-28  6:32       ` Sagi Grimberg
2017-08-28 19:15   ` Keith Busch
2017-08-23 17:58 ` [PATCH 06/10] nvme: track subsystems Christoph Hellwig
2017-08-23 22:04   ` Keith Busch [this message]
2017-08-24  8:52     ` Christoph Hellwig
2017-08-28  6:22   ` Sagi Grimberg
2017-08-23 17:58 ` [PATCH 07/10] nvme: track shared namespaces Christoph Hellwig
2017-08-28  6:51   ` Sagi Grimberg
2017-08-28  8:50     ` Christoph Hellwig
2017-08-28 20:21     ` J Freyensee
2017-08-29  8:25       ` Christoph Hellwig
2017-08-29  6:54     ` Guan Junxiong
2017-08-28 12:04   ` javigon
2017-08-28 12:41   ` Guan Junxiong
2017-08-28 14:30     ` Christoph Hellwig
2017-08-29  2:42       ` Guan Junxiong
2017-08-29  8:30         ` Christoph Hellwig
2017-08-29  8:29     ` Christoph Hellwig
2017-08-28 19:18   ` Keith Busch
2017-08-23 17:58 ` [PATCH 08/10] block: provide a generic_make_request_fast helper Christoph Hellwig
2017-08-28  7:00   ` Sagi Grimberg
2017-08-28  8:54     ` Christoph Hellwig
2017-08-28 11:01       ` Sagi Grimberg
2017-08-28 11:54         ` Christoph Hellwig
2017-08-28 12:38           ` Sagi Grimberg
2017-08-23 17:58 ` [PATCH 09/10] blk-mq: add a blk_steal_bios helper Christoph Hellwig
2017-08-28  7:04   ` Sagi Grimberg
2017-08-23 17:58 ` [PATCH 10/10] nvme: implement multipath access to nvme subsystems Christoph Hellwig
2017-08-23 18:21   ` Bart Van Assche
2017-08-24  8:59     ` hch
2017-08-24 20:17       ` Bart Van Assche
2017-09-05 11:53         ` Christoph Hellwig
2017-09-11  6:34           ` Tony Yang
2017-08-23 22:53   ` Keith Busch
2017-08-24  8:52     ` Christoph Hellwig
2017-08-28  7:23   ` Sagi Grimberg
2017-08-28  9:06     ` Christoph Hellwig
2017-08-28 13:40       ` Sagi Grimberg
2017-08-28 14:24         ` Christoph Hellwig
2017-09-07 15:17       ` Tony Yang
2017-08-29 10:22   ` Guan Junxiong
2017-08-29 14:51     ` Christoph Hellwig
2017-08-29 14:54   ` Keith Busch
2017-08-29 14:55     ` Christoph Hellwig
2017-08-29 15:41       ` Keith Busch
2017-09-18  0:17         ` 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=20170823220434.GB16596@localhost.localdomain \
    --to=keith.busch@intel.com \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox