From: hare@suse.de (Hannes Reinecke)
Subject: [PATCHv2 0/2] nvme-multipath: path selection fixes
Date: Thu, 4 Jul 2019 08:10:45 +0200 [thread overview]
Message-ID: <20190704061047.94976-1-hare@suse.de> (raw)
Hi all,
during analysing a mysterious failure due to blk_queue_split() (again)
I've found that the multipath path selection might return invalid
namespaces under certain circumstances.
This patchset fixes those scenarios.
As usual, reviews and comments are welcome.
Changes to v1:
- Use common helper nvme_path_is_disabled()
Hannes Reinecke (2):
nvme-multipath: check singular list in vme_round_robin_path()
nvme-multipath: do not select namespaces which are about to be removed
drivers/nvme/host/multipath.c | 18 +++++++++++++-----
1 file changed, 13 insertions(+), 5 deletions(-)
--
2.16.4
next reply other threads:[~2019-07-04 6:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-04 6:10 Hannes Reinecke [this message]
2019-07-04 6:10 ` [PATCH 1/2] nvme-multipath: check singular list in vme_round_robin_path() Hannes Reinecke
2019-07-04 6:10 ` [PATCH 2/2] nvme-multipath: do not select namespaces which are about to be removed Hannes Reinecke
2019-07-09 21:19 ` [PATCHv2 0/2] nvme-multipath: path selection fixes Christoph Hellwig
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=20190704061047.94976-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