From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH 0/3] Namespace iteration fixes
Date: Thu, 23 Jun 2016 11:29:03 -0600 [thread overview]
Message-ID: <1466702946-13065-1-git-send-email-keith.busch@intel.com> (raw)
Patch 1/3 cleanly applies to linux-block/for-linus and for-next. The
other two only apply to for-next.
The first fixes a bug introduced in 4.7 and hoping this can be applied
to 4.7. It's version 2 of this patch. The reset of the series is targeted
to 4.8.
The second patch fixes issues where buffered writers block removal
from proceeding.
The third locks the namespace mutex when searching for invalid
namespaces. While it doesn't appear necessary in the existing paths that
use it, it makes this function safe for potential future use.
Keith Busch (3):
nvme: Remove RCU namespace protection
nvme: Kill detached namespaces prior to removal
nvme: Put invalid namespaces on removal list
drivers/nvme/host/core.c | 112 ++++++++++++++++++++++++++++-------------------
1 file changed, 67 insertions(+), 45 deletions(-)
--
2.7.2
next reply other threads:[~2016-06-23 17:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-23 17:29 Keith Busch [this message]
2016-06-23 17:29 ` [PATCHv2 1/3] nvme: Remove RCU namespace protection Keith Busch
2016-06-28 8:31 ` Christoph Hellwig
2016-06-28 16:35 ` Keith Busch
2016-06-30 6:48 ` Christoph Hellwig
2016-06-30 14:57 ` Keith Busch
2016-06-30 22:59 ` Keith Busch
2016-06-23 17:29 ` [PATCH 2/3] nvme: Kill detached namespaces prior to removal Keith Busch
2016-06-28 8:32 ` Christoph Hellwig
2016-06-23 17:29 ` [PATCH 3/3] nvme: Put invalid namespaces on removal list Keith Busch
2016-06-28 8:32 ` Christoph Hellwig
2016-06-23 17:44 ` [PATCH 0/3] Namespace iteration fixes 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=1466702946-13065-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).