From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "snitzer@redhat.com" <snitzer@redhat.com>
Cc: "dm-devel@redhat.com" <dm-devel@redhat.com>
Subject: Re: Revert "dm mpath: remove unnecessary NVMe branching in favor of scsi_dh checks"
Date: Mon, 12 Mar 2018 21:32:39 +0000 [thread overview]
Message-ID: <1520890358.3469.68.camel@wdc.com> (raw)
In-Reply-To: <20180312212314.GA30763@redhat.com>
On Mon, 2018-03-12 at 17:23 -0400, Mike Snitzer wrote:
> Could you provide more details on your setup?
>
> Obviously you're using "queue_mode mq", what are your underlying paths?
>
> Given the trace it would seem you're hitting multipath_clone_and_map()'s
> blk_queue_dying(q) error path that calls activate_or_offline_path().
Hello Mike,
The reported kernel crash was triggered by running the following command:
srp-test/run_tests -c -d -r 10 -t 02-mq
The srp-test software is available at https://github.com/bvanassche/srp-test.
All patches necessary to run that script in a virtual machine (RoCE support
for the SRP initiator and target drivers) will be sent to Linus during the
kernel v4.17 merge window. These patches are already available in linux-next
today. Although I have not tried this myself, I expect that if you run the
above command against a kernel built from the linux-next code that that will
allow you to reproduce what I reported.
Thanks,
Bart.
next prev parent reply other threads:[~2018-03-12 21:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 20:28 [PATCH] Revert "dm mpath: remove unnecessary NVMe branching in favor of scsi_dh checks" Bart Van Assche
2018-03-12 21:23 ` Mike Snitzer
2018-03-12 21:32 ` Bart Van Assche [this message]
2018-03-13 1:23 ` Mike Snitzer
2018-03-13 16:43 ` Bart Van Assche
2018-03-13 17:02 ` Mike Snitzer
2018-03-13 17:07 ` Mike Snitzer
2018-03-13 17:10 ` Bart Van Assche
2018-03-13 21:41 ` Mike Snitzer
2018-03-14 16:34 ` Bart Van Assche
2018-03-13 15:25 ` Mike Snitzer
2018-03-13 16:31 ` Mike Snitzer
2018-03-13 16:46 ` Bart Van Assche
2018-03-13 16:58 ` Mike Snitzer
2018-03-30 17:04 ` Bart Van Assche
2018-03-13 16:38 ` Bart Van Assche
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=1520890358.3469.68.camel@wdc.com \
--to=bart.vanassche@wdc.com \
--cc=dm-devel@redhat.com \
--cc=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;
as well as URLs for NNTP newsgroup(s).