From: Christoph Hellwig <hch@lst.de>
To: John Meneghini <jmeneghi@redhat.com>
Cc: Chaitanya Kulkarni <chaitanyak@nvidia.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
Christoph Hellwig <hch@lst.de>,
"kbusch@kernel.org" <kbusch@kernel.org>,
Sagi Grimberg <sagi@grimberg.me>,
Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
Ewan Milne <emilne@redhat.com>,
Randy Jennings <randyj@purestorage.com>
Subject: Re: blktests nvme/052 failure
Date: Wed, 3 Jul 2024 06:35:49 +0200 [thread overview]
Message-ID: <20240703043549.GA24378@lst.de> (raw)
In-Reply-To: <7c0621e9-3af3-4ba9-ad96-3f322adc5a57@redhat.com>
On Tue, Jul 02, 2024 at 03:38:40PM -0400, John Meneghini wrote:
> Looks like I didn't test my queue-depth patches with blktests.
>
> I'll pull the new nvme-6.11 branch and try running this test now.
nvme/052 is a known issue in nvme-6.11 and for-6.11/block. It has been
fixes in 6.10-rc, but only after for-6.11/block branched off.
prev parent reply other threads:[~2024-07-03 4:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 5:24 blktests nvme/052 failure Chaitanya Kulkarni
2024-07-02 19:38 ` John Meneghini
2024-07-03 4:35 ` Christoph Hellwig [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=20240703043549.GA24378@lst.de \
--to=hch@lst.de \
--cc=chaitanyak@nvidia.com \
--cc=emilne@redhat.com \
--cc=jmeneghi@redhat.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=randyj@purestorage.com \
--cc=sagi@grimberg.me \
--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 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.