From: Matias <mb@lightnvm.io>
To: Wenwei Tao <ww.tao0320@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-block@vger.kernel.org
Subject: Re: [PATCH] lightnvm: remove targets when corresponding nvm device exit
Date: Tue, 24 Nov 2015 19:51:01 +0100 [thread overview]
Message-ID: <5654B195.4050406@lightnvm.io> (raw)
In-Reply-To: <1448380988-3988-1-git-send-email-ww.tao0320@gmail.com>
On 11/24/2015 05:03 PM, Wenwei Tao wrote:
> the target should be unreachable when underlying device was gone.
>
> Signed-off-by: Wenwei Tao <ww.tao0320@gmail.com>
> ---
> drivers/lightnvm/core.c | 12 ++++++++++--
> 1 file changed, 10 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/lightnvm/core.c b/drivers/lightnvm/core.c
> index f659e60..b95c6c4 100644
> --- a/drivers/lightnvm/core.c
> +++ b/drivers/lightnvm/core.c
> @@ -278,10 +278,18 @@ err:
> return ret;
> }
>
> +static void nvm_remove_target(struct nvm_target *t);
> +
You can move the hole declaration up here.
> static void nvm_exit(struct nvm_dev *dev)
> {
> + struct nvm_target *t, *n;
> +
> if (dev->ppalist_pool)
> dev->ops->destroy_dma_pool(dev->ppalist_pool);
> + down_write(&nvm_lock);
> + list_for_each_entry_safe(t, n, &dev->online_targets, list)
> + nvm_remove_target(t);
> + up_write(&nvm_lock);
list_for_each_entry_safe should be enough here.
Actually, we should properly block any creations of new targets when
nvm_exit is called. To prevent new ones to be created while we clean up.
Let me know if you want to submit a patch for this. Else I'll just apply
this one with the suggested changes. Thanks Tao.
> nvm_free(dev);
>
> pr_info("nvm: successfully unloaded\n");
> @@ -496,13 +504,13 @@ static int __nvm_configure_create(struct nvm_ioctl_create *create)
>
> static int __nvm_configure_remove(struct nvm_ioctl_remove *remove)
> {
> - struct nvm_target *t = NULL;
> + struct nvm_target *n, *t = NULL;
> struct nvm_dev *dev;
> int ret = -1;
>
> down_write(&nvm_lock);
> list_for_each_entry(dev, &nvm_devices, devices)
> - list_for_each_entry(t, &dev->online_targets, list) {
> + list_for_each_entry_safe(t, n, &dev->online_targets, list) {
> if (!strcmp(remove->tgtname, t->disk->disk_name)) {
> nvm_remove_target(t);
> ret = 0;
>
next prev parent reply other threads:[~2015-11-24 18:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 16:03 Wenwei Tao
2015-11-24 18:51 ` Matias [this message]
2015-11-25 9:23 ` Wenwei Tao
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=5654B195.4050406@lightnvm.io \
--to=mb@lightnvm.io \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ww.tao0320@gmail.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
Powered by JetHome