From: Bart Van Assche <bvanassche@acm.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
Mike Snitzer <snitzer@redhat.com>
Subject: Re: for-next branch and blktests/srp
Date: Thu, 06 Dec 2018 09:19:31 -0800 [thread overview]
Message-ID: <1544116771.185366.261.camel@acm.org> (raw)
In-Reply-To: <41bbac1e-7461-4378-a18d-531b625d6784@kernel.dk>
On Thu, 2018-12-06 at 10:00 -0700, Jens Axboe wrote:
> On 12/6/18 9:47 AM, Bart Van Assche wrote:
> > If I merge Jens' for-next branch with Linus' master branch, boot the
> > resulting kernel in a VM and run blktests/tests/srp/002 then that test
> > never finishes. The same test passes against Linus' master branch. I
> > think this is a regression. The following appears in the system log if
> > I run that test:
>
> You are running that test on a dm device? Can you shed some light on
> how that dm device is setup?
Hi Jens,
The dm device referred to in my e-mail is a dm-mpath device created by test
srp/002. All parameters of that device are under control of that test script.
From the srp/002 test script:
DESCRIPTION="File I/O on top of multipath concurrently with logout and login (mq)"
From srp/multipath.conf:
defaults {
find_multipaths no
user_friendly_names yes
queue_without_daemon no
}
devices {
device {
vendor "LIO-ORG|SCST_BIO|FUSIONIO"
product ".*"
features "1 queue_if_no_path"
path_checker tur
}
}
Bart.
next prev parent reply other threads:[~2018-12-06 17:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 16:47 for-next branch and blktests/srp Bart Van Assche
2018-12-06 17:00 ` Jens Axboe
2018-12-06 17:19 ` Bart Van Assche [this message]
2018-12-06 17:28 ` Jens Axboe
2018-12-06 17:48 ` Jens Axboe
2018-12-06 18:02 ` Bart Van Assche
2018-12-06 18:08 ` Jens Axboe
2018-12-06 18:10 ` Bart Van Assche
2018-12-06 18:12 ` Jens Axboe
2018-12-06 18:16 ` Bart Van Assche
2018-12-06 20:56 ` Bart Van Assche
2018-12-06 21:04 ` Jens Axboe
2018-12-06 22:15 ` Jens Axboe
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=1544116771.185366.261.camel@acm.org \
--to=bvanassche@acm.org \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.