From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH v2] nvmet: Fix possible infinite loop triggered on hot namespace removal
Date: Wed, 2 Nov 2016 15:40:45 +0100 [thread overview]
Message-ID: <20161102144045.GB13577@lst.de> (raw)
In-Reply-To: <1478015644-26108-1-git-send-email-sagi@grimberg.me>
On Tue, Nov 01, 2016@05:54:04PM +0200, Sagi Grimberg wrote:
> From: Solganik Alexander <sashas at lightbitslabs.com>
>
> When removing a namespace we delete it from the subsystem namespaces
> list with list_del_init which allows us to know if it is enabled or
> not.
>
> The problem is that list_del_init initialize the list next and does
> not respect the RCU list-traversal we do on the IO path for locating
> a namespace. Instead we need to use list_del_rcu which is allowed to
> run concurrently with the _rcu list-traversal primitives (keeps list
> next intact) and guarantees concurrent nvmet_find_naespace forward
> progress.
>
> By changing that, we cannot rely on ns->dev_link for knowing if the
> namspace is enabled, so add enabled indicator entry to nvmet_ns for
> that.
>
> Signed-off-by: Sagi Grimberg <sagi at grimberg.me>
> Signed-off-by: Solganik Alexander <sashas at lightbitslabs.com>
> Cc: <stable at vger.kernel.org> # v4.8+
> ---
> Changes from v1:
> - Changed enabled from atomic bit to bool and updated it under
> the subsys lock in order to protect against enable/disable
> running concurrently
> - Fixed nvmet_ns_enabled display
>
> drivers/nvme/target/core.c | 15 +++++++++------
> drivers/nvme/target/nvmet.h | 3 ++-
> 2 files changed, 11 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/nvme/target/core.c b/drivers/nvme/target/core.c
> index 6559d5afa7bf..bf36d2486245 100644
> --- a/drivers/nvme/target/core.c
> +++ b/drivers/nvme/target/core.c
> @@ -264,9 +264,11 @@ int nvmet_ns_enable(struct nvmet_ns *ns)
> int ret = 0;
>
> mutex_lock(&subsys->lock);
> - if (!list_empty(&ns->dev_link))
> + if (ns->enabled)
> goto out_unlock;
>
> + ns->enabled = true;
> +
> ns->bdev = blkdev_get_by_path(ns->device_path, FMODE_READ | FMODE_WRITE,
> NULL);
> if (IS_ERR(ns->bdev)) {
This will leave the enable flag set when an error happen? later,
won't it? I'd set it just before dropping the lock.
> static inline bool nvmet_ns_enabled(struct nvmet_ns *ns)
> {
> - return !list_empty_careful(&ns->dev_link);
> + return ns->enabled;
and we can probably kill this helper, it's pretty pointless
now.
next prev parent reply other threads:[~2016-11-02 14:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-01 15:54 [PATCH v2] nvmet: Fix possible infinite loop triggered on hot namespace removal Sagi Grimberg
2016-11-02 14:40 ` Christoph Hellwig [this message]
2016-11-03 21:20 ` Sagi Grimberg
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=20161102144045.GB13577@lst.de \
--to=hch@lst.de \
/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).