From: hare@suse.de (Hannes Reinecke)
Subject: [PATCH 0/2] skip removed namespaces
Date: Thu, 1 Aug 2019 09:16:42 +0200 [thread overview]
Message-ID: <20190801071644.66690-1-hare@suse.de> (raw)
Hi all,
when traversing the namespaces lists we need to ensure to skip
any namespaces marked as 'REMOVING', as these are about to be
deleted and shouldn't be accessed anymore.
As usual, comments and reviews are welcome.
Hannes Reinecke (2):
nvme: skip namespaces which are about to be removed
nvme: do not remove namespaces during reset
drivers/nvme/host/core.c | 44 ++++++++++++++++++++++++++++++++++++++++----
1 file changed, 40 insertions(+), 4 deletions(-)
--
2.16.4
next reply other threads:[~2019-08-01 7:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-01 7:16 Hannes Reinecke [this message]
2019-08-01 7:16 ` [PATCH 1/2] nvme: skip namespaces which are about to be removed Hannes Reinecke
2019-08-01 18:13 ` Nadolski, Edmund
2019-08-01 18:34 ` Sagi Grimberg
2019-08-01 21:36 ` Keith Busch
2019-08-01 21:52 ` Sagi Grimberg
2019-08-01 22:10 ` Keith Busch
2019-08-02 20:45 ` Sagi Grimberg
2019-08-01 7:16 ` [PATCH 2/2] nvme: do not remove namespaces during reset Hannes Reinecke
2019-08-01 18:15 ` Nadolski, Edmund
2019-08-01 18:42 ` 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=20190801071644.66690-1-hare@suse.de \
--to=hare@suse.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