From: Kent Overstreet <kent.overstreet@linux.dev>
To: Daniel Wagner <dwagner@suse.de>
Cc: Christoph Hellwig <hch@infradead.org>, Coly Li <colyli@fnnas.com>,
axboe@kernel.dk, linux-block@vger.kernel.org,
linux-bcache@vger.kernel.org,
Shida Zhang <zhangshida@kylinos.cn>
Subject: Re: [PATCH] Revert "bcache: fix improper use of bi_end_io"
Date: Mon, 19 Jan 2026 05:18:15 -0500 [thread overview]
Message-ID: <aW4D0UPTBXEap1Jg@moria.home.lan> (raw)
In-Reply-To: <f7af1e25-fbe9-4d37-b902-5b3a9ed4c8f4@flourine.local>
On Mon, Jan 19, 2026 at 10:51:46AM +0100, Daniel Wagner wrote:
> On Tue, Jan 13, 2026 at 11:34:18AM -0500, Kent Overstreet wrote:
> > Coly and I were just on a call discussing updating my old test suite. I
> > haven't used the bcache tests in > 10 years so they do need to be
> > updated, but the harness and related tooling is well supported both for
> > local development and has full CI.
> >
> > https://evilpiepirate.org/git/ktest.git/tree/README.md
> > https://evilpiepirate.org/git/ktest.git/tree/tests/bcache/
>
> I just quickly look at the tests and I got the impression some of those
> tests could be added to blktests. blktests is run by various people,
> thus bcache would get some basic test exposure, e.g. in linux-next.
ktest has features that blktests/fstests don't - it's a full testrunner,
with a CI and test dashboard, with subtest level sharding that runs on
entire cluster.
What would make sense would be for ktest to wrap blktests, like it
already does fstests.
next prev parent reply other threads:[~2026-01-19 10:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 6:09 [PATCH] Revert "bcache: fix improper use of bi_end_io" colyli
2026-01-13 8:07 ` Christoph Hellwig
2026-01-13 8:30 ` Kent Overstreet
2026-01-13 8:34 ` Christoph Hellwig
2026-01-13 8:39 ` Kent Overstreet
2026-01-13 8:58 ` Christoph Hellwig
2026-01-13 9:27 ` Kent Overstreet
2026-01-13 15:00 ` Christoph Hellwig
2026-01-13 15:30 ` Kent Overstreet
2026-01-13 16:18 ` Coly Li
2026-01-13 16:26 ` Christoph Hellwig
2026-01-13 16:34 ` Kent Overstreet
2026-01-19 9:51 ` Daniel Wagner
2026-01-19 10:18 ` Kent Overstreet [this message]
2026-01-19 10:34 ` Daniel Wagner
2026-01-19 15:57 ` Daniel Wagner
2026-01-13 16:22 ` Coly Li
2026-01-13 16:25 ` Christoph Hellwig
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=aW4D0UPTBXEap1Jg@moria.home.lan \
--to=kent.overstreet@linux.dev \
--cc=axboe@kernel.dk \
--cc=colyli@fnnas.com \
--cc=dwagner@suse.de \
--cc=hch@infradead.org \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=zhangshida@kylinos.cn \
/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