From: Bart Van Assche <bvanassche@acm.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
Logan Gunthorpe <logang@deltatee.com>
Subject: Re: Kernel v5.0-rc1 and blk-mq
Date: Mon, 07 Jan 2019 13:30:01 -0800 [thread overview]
Message-ID: <1546896601.83374.26.camel@acm.org> (raw)
In-Reply-To: <1546896114.83374.22.camel@acm.org>
On Mon, 2019-01-07 at 13:21 -0800, Bart Van Assche wrote:
> When I tried to run the SRP tests from the blktests repository against the
> v5.0 kernel several issues were reported. The same tests pass against kernel
> v4.20.
A correction: this was triggered by a new test ("Run sg_reset while I/O is ongoing").
Anyway, I don't think that such a test should trigger the following statement in
blk_mq_start_request():
WARN_ON_ONCE(blk_mq_rq_state(rq) != MQ_RQ_IDLE);
A few kernel versions back I ran sg_reset manually while I/O was ongoing and that
test passed. So this test result may indicate an issue in the blk-mq request state
rework.
Bart.
prev parent reply other threads:[~2019-01-07 21:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 21:21 Kernel v5.0-rc1 and blk-mq Bart Van Assche
2019-01-07 21:30 ` Bart Van Assche [this message]
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=1546896601.83374.26.camel@acm.org \
--to=bvanassche@acm.org \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=logang@deltatee.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.