Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: sunad.s@samsung.com (Sunad Bhandary)
Subject: [PATCHv2] NVMe: Fix removal in case of active namespace list scanning method
Date: Mon, 30 May 2016 16:15:41 +0530	[thread overview]
Message-ID: <574C19D5.1060106@samsung.com> (raw)
In-Reply-To: <20160527132834.GA19990@localhost.localdomain>

>We don't want to remove the namespaces on error here. That could
>remove valid, in use namespaces: if nvme_identify_ns_list fails (maybe
>controller just doesn't support that identify mode), we do the
>sequential scanning.

>Just leave the 'goto free' alone, and call
>nvme_remove_invalid_namespaces only on success.

In the patch, the namespaces are not removed on failure of identify
list. If nvme_identify_ns_list fails, the value is returned and
sequential scanning is done. The call to nvme_remove_invalid_namespaces 
is done when the value of nsid in the list is 0.

Snapshot of patch:
  ....
	ret = nvme_identify_ns_list(ctrl, prev, ns_list);
                 if (ret)
                         goto free;
  ....
  	nsid = le32_to_cpu(ns_list[j]);
                         if (!nsid)
                                 goto out;
  ....

  out:
         nvme_remove_invalid_namespaces(ctrl, prev);
  free:
         kfree(ns_list);
         return ret;

This should be able to handle error scenarios or am I missing something?

Thanks and Regards,
Sunad

  reply	other threads:[~2016-05-30 10:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-27 10:29 [PATCHv2] NVMe: Fix removal in case of active namespace list scanning method Sunad Bhandary S
2016-05-27 13:28 ` Keith Busch
2016-05-30 10:45   ` Sunad Bhandary [this message]
2016-05-31 14:35     ` Keith Busch
2016-06-08  5:13       ` Sunad Bhandary

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=574C19D5.1060106@samsung.com \
    --to=sunad.s@samsung.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