From: "Coly Li" <colyli@fnnas.com>
To: "Christoph Hellwig" <hch@infradead.org>
Cc: "Stephen Zhang" <starzhangzsd@gmail.com>,
<kent.overstreet@linux.dev>, <axboe@kernel.dk>,
<sashal@kernel.org>, <linux-bcache@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <zhangshida@kylinos.cn>
Subject: Re: [PATCH] bcache: fix double bio_endio completion in detached_dev_end_io
Date: Mon, 19 Jan 2026 16:19:38 +0800 [thread overview]
Message-ID: <aW3nzb2lOSVSbqQZ@studio.local> (raw)
In-Reply-To: <aW3Sq4H_OosPVaNe@infradead.org>
On Sun, Jan 18, 2026 at 10:43:55PM +0800, Christoph Hellwig wrote:
> On Sun, Jan 18, 2026 at 07:49:36PM +0800, Coly Li wrote:
> > Shida,
> > can you also test it and confirm? We need to get the fix in within 6.19 cycle.
> >
> > Yes, we need to make a dicision ASAP.
> > I prefer the clone bio solution, and it looks fine to me.
>
> Do you have any maintainer QA that exercises this? For basically any
Normally I do testing by following methods,
1) normal file system testing on it
2) long time I/O pressure e.g. at least 48 hours
3) deploy on my working machines with real workload for weeks
Current tests are not automatically. And I will integreate Kent's test
tools in.
> other maintained subsystem we'd have a maintainer jump on verity fixes
> like this ASAP and test them.
>
Before I work on it, I want to know the author already ran and tested the
patch firstly. Normally I won't test any patches posted on mailing list.
Thanks.
Coly Li
next prev parent reply other threads:[~2026-01-19 8:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 7:48 [PATCH] bcache: fix double bio_endio completion in detached_dev_end_io zhangshida
2026-01-15 8:06 ` Stephen Zhang
2026-01-15 8:29 ` Christoph Hellwig
2026-01-18 11:49 ` Coly Li
2026-01-19 6:43 ` Christoph Hellwig
2026-01-19 8:19 ` Coly Li [this message]
2026-01-19 8:29 ` Christoph Hellwig
2026-01-19 8:51 ` Coly Li
2026-01-19 6:53 ` Stephen Zhang
2026-01-19 8:04 ` Christoph Hellwig
2026-01-15 8:59 ` Kent Overstreet
2026-01-15 9:17 ` Stephen Zhang
2026-01-15 9:28 ` Kent Overstreet
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=aW3nzb2lOSVSbqQZ@studio.local \
--to=colyli@fnnas.com \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=starzhangzsd@gmail.com \
--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