From: Christoph Hellwig <hch@infradead.org>
To: Daniel Wagner <dwagner@suse.de>
Cc: Christoph Hellwig <hch@infradead.org>,
Stephen Zhang <starzhangzsd@gmail.com>,
Kent Overstreet <kent.overstreet@linux.dev>,
Coly Li <colyli@fnnas.com>,
Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
linux-block@vger.kernel.org, linux-bcache@vger.kernel.org
Subject: Re: [PATCH blktests] bcache: add bcache/001
Date: Tue, 20 Jan 2026 23:56:33 -0800 [thread overview]
Message-ID: <aXCGseCNoaX8rQ83@infradead.org> (raw)
In-Reply-To: <20260120-bcache-v1-1-59bf0b2d4140@suse.de>
On Tue, Jan 20, 2026 at 02:28:18PM +0100, Daniel Wagner wrote:
> So far we are missing tests for bcache. Besides a relative simple
> setup/teardown tests add also the corresponding infrastructure. More
> tests are to be expected to depend on this.
>
> _create_bcache/_remove_bcache are tracking the resources and if anything
> is missing it will complain.
Not really an expert on bcache, and not that much in blktests either,
but having some testing for bcache readabily available is fantastic!
> Note: to run this tests blktests TEST_CASE_DEV_ARRAY needs to be set:
>
> # cat config
> TEST_CASE_DEV_ARRAY[bcache/*]="/dev/nvme0n1 /dev/vdb /dev/vdc"
Can you add a blurb to Documentation/running-tests.md about this?
I also wonder if we could have a generic TEST_CASE_DEV_ARRAY that
would just work for all tests needing multiple devices?
next prev parent reply other threads:[~2026-01-21 7:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 13:28 [PATCH blktests] bcache: add bcache/001 Daniel Wagner
2026-01-21 7:56 ` Christoph Hellwig [this message]
2026-01-21 12:48 ` Daniel Wagner
2026-01-22 6:35 ` Christoph Hellwig
2026-01-22 9:13 ` Shinichiro Kawasaki
2026-01-21 8:19 ` Johannes Thumshirn
2026-01-21 12:36 ` Daniel Wagner
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=aXCGseCNoaX8rQ83@infradead.org \
--to=hch@infradead.org \
--cc=colyli@fnnas.com \
--cc=dwagner@suse.de \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=shinichiro.kawasaki@wdc.com \
--cc=starzhangzsd@gmail.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