From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH 0/2] Namespace attachment fixes/simplifications
Date: Thu, 1 Oct 2015 17:14:09 -0600 [thread overview]
Message-ID: <1443741251-13274-1-git-send-email-keith.busch@intel.com> (raw)
This started off investigating a suggestion Christoph made on the awkward
way the driver removes disks if the controller can't handle IO after
attempting a resume from suspend.
It turns out that it has been a LONG time since the error path from
resume was tested. It definitely was broken, so this turned into a two
part series. I can split 2/2 into a two more if anyone thinks changes
are unrelated.
>From testing it became clear that it is not sufficient to reference count
only the controller anymore. Jens suggested a while back to reference
count the namespaces, but I didn't think there was a need since namespaces
couldn't be deleted while the controller had active references anyway. Now
that namespaces can be deleted independent of the controller, we really
do need a separate reference count.
Keith Busch (2):
NVMe: Reference count open namespaces
NVMe: Simplify device resume on io queue failure
drivers/block/nvme-core.c | 80 ++++++++++++++++++---------------------------
include/linux/nvme.h | 2 +-
2 files changed, 32 insertions(+), 50 deletions(-)
--
1.7.10.4
next reply other threads:[~2015-10-01 23:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 23:14 Keith Busch [this message]
2015-10-01 23:14 ` [PATCH 1/2] NVMe: Reference count open namespaces Keith Busch
2015-10-02 12:59 ` Christoph Hellwig
2015-10-02 14:26 ` Keith Busch
2015-10-02 14:31 ` Christoph Hellwig
2015-10-01 23:14 ` [PATCH 2/2] NVMe: Simplify device resume on io queue failure Keith Busch
2015-10-02 13:03 ` Christoph Hellwig
2015-10-02 14:17 ` Keith Busch
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=1443741251-13274-1-git-send-email-keith.busch@intel.com \
--to=keith.busch@intel.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;
as well as URLs for NNTP newsgroup(s).