From: Luis Chamberlain <mcgrof@kernel.org>
To: linux-block@vger.kernel.org, jejb@linux.ibm.com,
martin.petersen@oracle.com
Cc: Luis Chamberlain <mcgrof@kernel.org>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: blktests: block/009 next-20210304 failure rate average of 1/448
Date: Tue, 16 Mar 2021 17:46:45 +0000 [thread overview]
Message-ID: <20210316174645.GI4332@42.do-not-panic.com> (raw)
I've managed to reproduce blktests block/009 failures with kdevops [0]
on linux-next tag next-20210304 with a current failure rate average of
1/448 (3 counted failures so far). I've documented the failure on
korg#212305 [1] and provide instructions on how to reproduce. The
failure happens on KVM virtualized guests, for the host OS I am
using debian testing, but the target kernel is linux-next.
My personal suspicion is not on the block layer but on scsi_debug
because this can fail:
modprobe scsi_debug; rmmod scsi_debug
This second issue may be a secondary separate issue, but I figured
I'd mention it. To fix this later issue I've looked at ways to
make scsi_debug_init() wait until its scsi devices are probed,
however its not clear how to do this correctly. If someone has
an idea let me know. If that fixes this issue then we know it was
that.
[0] https://github.com/mcgrof/kdevops
[1] https://bugzilla.kernel.org/show_bug.cgi?id=212305
Luis
next reply other threads:[~2021-03-16 17:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 17:46 Luis Chamberlain [this message]
2021-03-16 18:47 ` blktests: block/009 next-20210304 failure rate average of 1/448 Luis Chamberlain
2021-03-18 19:33 ` Luis Chamberlain
2021-03-18 17:54 ` Luis Chamberlain
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=20210316174645.GI4332@42.do-not-panic.com \
--to=mcgrof@kernel.org \
--cc=jejb@linux.ibm.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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).