From: Christoph Hellwig <hch@infradead.org>
To: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: blktests failures with v5.19-rc1
Date: Fri, 10 Jun 2022 01:07:06 -0700 [thread overview]
Message-ID: <YqL7qr6p1qDImkni@infradead.org> (raw)
In-Reply-To: <20220609235329.4jbz4wr3eg2nmzqa@shindev>
On Thu, Jun 09, 2022 at 11:53:30PM +0000, Shinichiro Kawasaki wrote:
> Failure descriptiion
> ====================
> #1: block/002: Failed 3 times with 3 trials.
> Known issue. It is suggested to remove this test case [1].
> [1] https://lore.kernel.org/linux-block/20220530134548.3108185-3-hch@lst.de/
It's a little more complicated than that. The patch mentioned there
isn't actually in 5.19-rc yet. But even the current code doesn't remove
synchronously, so it could happen (although I don't see it).
I'll send a patch to remove this particular check, the test case itself
can mostly remain.
next prev parent reply other threads:[~2022-06-10 8:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 23:53 blktests failures with v5.19-rc1 Shinichiro Kawasaki
2022-06-10 8:07 ` Christoph Hellwig [this message]
2022-06-10 9:22 ` Chaitanya Kulkarni
2022-06-10 9:32 ` Chaitanya Kulkarni
2022-06-10 12:25 ` Shinichiro Kawasaki
2022-06-10 13:15 ` Yi Zhang
2022-06-10 14:47 ` Keith Busch
2022-06-11 8:34 ` Yi Zhang
2022-06-14 1:09 ` Shinichiro Kawasaki
2022-06-14 2:23 ` Keith Busch
2022-06-14 2:38 ` Chaitanya Kulkarni
2022-06-14 4:00 ` Shinichiro Kawasaki
2022-06-15 19:47 ` Bjorn Helgaas
2022-06-15 22:01 ` Chaitanya Kulkarni
2022-06-15 23:13 ` Yi Zhang
2022-06-16 4:42 ` Shinichiro Kawasaki
2022-06-16 17:55 ` Chaitanya Kulkarni
2022-06-15 23:16 ` Keith Busch
2022-07-19 4:50 ` Shinichiro Kawasaki
2022-07-19 22:31 ` Bjorn Helgaas
2022-07-20 2:27 ` Shinichiro Kawasaki
2022-12-19 11:27 ` Shinichiro Kawasaki
2022-12-29 18:13 ` Bjorn Helgaas
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=YqL7qr6p1qDImkni@infradead.org \
--to=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=shinichiro.kawasaki@wdc.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