From: Mike Snitzer <snitzer@redhat.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Jens Axboe <axboe@kernel.dk>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
dm-devel@redhat.com
Subject: Re: for-next hangs on test srp/012
Date: Tue, 11 Dec 2018 18:05:14 -0500 [thread overview]
Message-ID: <20181211230514.GA20445@redhat.com> (raw)
In-Reply-To: <1544569107.185366.391.camel@acm.org>
On Tue, Dec 11 2018 at 5:58pm -0500,
Bart Van Assche <bvanassche@acm.org> wrote:
> Hi Jens,
>
> If I run the following subset of blktests:
>
> while :; do ./check -q srp && ./check -q nvmeof-mp; done
>
> against today's for-next branch (commit dd2bf2df85a7) then after some
> time the following hang is reported:
Jens has applied a fix from me today that I think is very relevant;
it'll be in tomorrow's for-next:
http://git.kernel.dk/cgit/linux-block/commit/?h=for-4.21/block&id=c4576aed8d85d808cd6443bda58393d525207d01
Please try with that and see how things go.
Thanks,
Mike
next prev parent reply other threads:[~2018-12-11 23:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 22:58 for-next hangs on test srp/012 Bart Van Assche
2018-12-11 23:05 ` Mike Snitzer [this message]
2018-12-11 23:09 ` Bart Van Assche
2018-12-11 23:09 ` Bart Van Assche
2018-12-12 0:22 ` Mike Snitzer
2018-12-12 0:02 ` Jens Axboe
2018-12-12 0:18 ` Bart Van Assche
2018-12-12 0:19 ` Ming Lei
2018-12-12 0:27 ` Mike Snitzer
2018-12-12 0:38 ` Ming Lei
2018-12-12 1:05 ` Jens Axboe
2018-12-12 1:23 ` Jens Axboe
2018-12-12 1:36 ` Jens Axboe
2018-12-12 1:43 ` Ming Lei
2018-12-12 1:44 ` Jens Axboe
2018-12-12 1:49 ` Ming Lei
2018-12-12 2:03 ` Ming Lei
2018-12-12 2:25 ` Jens Axboe
2018-12-12 4:28 ` Ming Lei
2018-12-12 1:37 ` Ming Lei
2018-12-12 1:39 ` 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=20181211230514.GA20445@redhat.com \
--to=snitzer@redhat.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=dm-devel@redhat.com \
--cc=linux-block@vger.kernel.org \
/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.