From: snitzer@redhat.com (Mike Snitzer)
Subject: 'modprobe nvme_core multipath=N' crashes in face of multipath fabric
Date: Wed, 11 Apr 2018 10:17:21 -0400 [thread overview]
Message-ID: <20180411141720.GB22124@redhat.com> (raw)
In-Reply-To: <20180411134530.GC9238@localhost.localdomain>
On Wed, Apr 11 2018 at 9:45am -0400,
Keith Busch <keith.busch@intel.com> wrote:
> On Tue, Apr 10, 2018@04:49:53PM -0400, Mike Snitzer wrote:
> > This isn't new since the 4.17 merge or anything, I first noticed this
> > issue existed while using a 4.16-rc4 kernel.
> >
> > modprobe nvme_core multipath=N
>
> Thanks for the notice.
>
> There is definitely a bug here when CONFIG_NVME_MULTIPATH=y but nvme_core
> multipath is disabled in the presence of shared namespaces. I think we'd
> need each namespace to get a different "head" out of the subsystem in
> this case, but it may take a moment for me to detangle this.
No problem, it certainly isn't something I could tackle any quicker ;)
Thanks for looking to resolve this though.
next prev parent reply other threads:[~2018-04-11 14:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-10 20:49 'modprobe nvme_core multipath=N' crashes in face of multipath fabric Mike Snitzer
2018-04-11 13:45 ` Keith Busch
2018-04-11 14:17 ` Mike Snitzer [this message]
2018-04-11 17:58 ` Keith Busch
2018-04-11 21:46 ` Mike Snitzer
2018-04-12 8:12 ` Sagi Grimberg
2018-04-12 22:28 ` 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=20180411141720.GB22124@redhat.com \
--to=snitzer@redhat.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