From: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: Daniel Wagner <dwagner@suse.de>
Cc: "hch@infradead.org" <hch@infradead.org>,
Stephen Zhang <starzhangzsd@gmail.com>,
Kent Overstreet <kent.overstreet@linux.dev>,
Coly Li <colyli@fnnas.com>,
Johannes Thumshirn <Johannes.Thumshirn@wdc.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-bcache@vger.kernel.org" <linux-bcache@vger.kernel.org>
Subject: Re: [PATCH blktests v5 2/3] bcache: add bcache/002
Date: Sat, 7 Mar 2026 10:24:46 +0000 [thread overview]
Message-ID: <aav7vTM7IerMwsT4@shinmob> (raw)
In-Reply-To: <baa3a723-2f9c-4e10-9d42-b4152de92df2@flourine.local>
On Mar 06, 2026 / 14:14, Daniel Wagner wrote:
> On Fri, Mar 06, 2026 at 12:27:51PM +0000, Shinichiro Kawasaki wrote:
> > On Mar 05, 2026 / 16:01, Daniel Wagner wrote:
> > > Add test case from Stephen Zhang [1][2], which is
> > >
> > > 1. Wait for fio to complete (wait $fio_pid)
> > > 2. Wait a few seconds for I/O to drain
> > > 3. Then check the utilization
> > >
> > > If utilization is still > 0% after I/O completes, then there's a real
> > > accounting leak.
> > >
> > > [1] https://lore.kernel.org/linux-bcache/CANubcdX7eNbH_bo4-f94DUbdiEbt04Vxy1MPyhm+CZyXB01FuQ@mail.gmail.com/
> > > [2] https://lore.kernel.org/all/CANubcdU92Uv7wNdZH357LLTnfwPouekXNTPSjHnzYzK99-eZ9w@mail.gmail.com
> >
> > Thanks for the updates. It's good that we do not need iostat :)
> >
> > I ran this test case with v7.0-rc2 kernel, and it passes. Good.
> >
> > I also ran this test case with older kernel without the kernel fix [1]. I
> > expected failure, but it passed. I ran the Stephen's original test script and it
> > did not fail either. So I guess my test environment does not fulfill the
> > conditions to recreate the failure. Daniel, did you observe this test case
> > failed with any older kernel?
>
> Same here, it doesn't fail on older kernels either. Maybe we should just
> not merge this test then? Maybe Stephen can have a look and figure out
> what needs to be done to trigger the condition more reliable.
I see. Before merging this patch, I would like to make sure that this test case
is valuable, and it does not just waste time and power of CI systems.
Stephen,
May I ask you to share what kind of devices you used to recreate the failure?
Also, could you share the kernel .config to recreate the failure? I would like
use them to recreate the failure on my test system.
>
> > Let me leave nit comments in line. If this patch does not respin, I can fold in
> > the changes for the nit comments.
>
> Sure, just fix it up if you decide to apply it.
Got it, thanks.
next prev parent reply other threads:[~2026-03-07 10:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 15:01 [PATCH blktests v5 0/3] bcache: add initial test cases Daniel Wagner
2026-03-05 15:01 ` [PATCH blktests v5 1/3] bcache: add bcache/001 Daniel Wagner
2026-03-06 9:49 ` Johannes Thumshirn
2026-03-06 12:15 ` Shinichiro Kawasaki
2026-03-06 12:45 ` Daniel Wagner
2026-03-05 15:01 ` [PATCH blktests v5 2/3] bcache: add bcache/002 Daniel Wagner
2026-03-06 9:59 ` Johannes Thumshirn
2026-03-06 12:27 ` Shinichiro Kawasaki
2026-03-06 13:14 ` Daniel Wagner
2026-03-07 10:24 ` Shinichiro Kawasaki [this message]
2026-03-10 9:29 ` Stephen Zhang
2026-03-12 1:44 ` Shinichiro Kawasaki
2026-03-05 15:01 ` [PATCH blktests v5 3/3] doc: document how to configure bcache tests Daniel Wagner
2026-03-06 10:00 ` Johannes Thumshirn
2026-03-07 10:27 ` [PATCH blktests v5 0/3] bcache: add initial test cases Shinichiro Kawasaki
2026-03-09 9:40 ` 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=aav7vTM7IerMwsT4@shinmob \
--to=shinichiro.kawasaki@wdc.com \
--cc=Johannes.Thumshirn@wdc.com \
--cc=colyli@fnnas.com \
--cc=dwagner@suse.de \
--cc=hch@infradead.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--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