From: hare@suse.de (Hannes Reinecke)
Subject: [PATCH 0/2] nvme-multipath: path selection fixes
Date: Wed, 3 Jul 2019 15:12:30 +0200 [thread overview]
Message-ID: <20190703131232.58595-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.
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 | 13 ++++++++++---
1 file changed, 10 insertions(+), 3 deletions(-)
--
2.16.4
next reply other threads:[~2019-07-03 13:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-03 13:12 Hannes Reinecke [this message]
2019-07-03 13:12 ` [PATCH 1/2] nvme-multipath: check singular list in vme_round_robin_path() Hannes Reinecke
2019-07-03 13:12 ` [PATCH 2/2] nvme-multipath: do not select namespaces which are about to be removed Hannes Reinecke
2019-07-03 13:21 ` Christoph Hellwig
2019-07-03 20:33 ` Sagi Grimberg
2019-07-04 6:00 ` Hannes Reinecke
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=20190703131232.58595-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