From: hch <hch@lst.de>
To: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Cc: hch <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@kernel.dk>,
Keith Busch <kbusch@meta.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
Jirong Feng <jirong.feng@easystack.cn>
Subject: Re: [PATCH] nvme-loop: set blocking flag
Date: Wed, 23 Oct 2024 07:20:42 +0200 [thread overview]
Message-ID: <20241023052042.GB1341@lst.de> (raw)
In-Reply-To: <ygq2tospvgesry2uuhh2fh5gzdm3vbkatdm42v2fjqlddzj43d@sdoplqu4vg62>
On Tue, Oct 22, 2024 at 08:08:31AM +0000, Shinichiro Kawasaki wrote:
> As for the BUG caused by the commit 505363957fad, the blktests test case
> nvme/052 can confirm if any patch fixes the BUG or not. It is recreate in
> stable manner on my test node [1], so I'm happy to help testing.
>
> If you mean a test case to confirm that the commit 505363957fad achieves its
> purpose, I'm not sure about it. According to its commit log, I guess Jirong
> might have a test environment.
Yes, that's the main thing I want to be able to test.
next prev parent reply other threads:[~2024-10-23 5:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 17:20 [PATCH] nvme-loop: set blocking flag Keith Busch
2024-10-17 17:36 ` Bart Van Assche
2024-10-17 17:39 ` Jens Axboe
2024-10-17 18:04 ` Keith Busch
2024-10-18 5:10 ` Christoph Hellwig
2024-10-20 21:35 ` Sagi Grimberg
2024-10-22 6:28 ` Christoph Hellwig
2024-10-22 7:02 ` Christoph Hellwig
2024-10-22 8:08 ` Shinichiro Kawasaki
2024-10-23 5:20 ` hch [this message]
2024-10-22 9:26 ` Sagi Grimberg
2024-10-22 9:25 ` Sagi Grimberg
2024-10-18 5:10 ` Christoph Hellwig
2024-10-18 4:19 ` Shinichiro Kawasaki
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=20241023052042.GB1341@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=jirong.feng@easystack.cn \
--cc=kbusch@kernel.org \
--cc=kbusch@meta.com \
--cc=linux-nvme@lists.infradead.org \
--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.