linux-kernel - Re: [PATCH] bcache: fix double bio_endio completion in detached_dev_end

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <aW3nzb2lOSVSbqQZ@studio.local>
Date: Mon, 19 Jan 2026 16:19:38 +0800
From: "Coly Li" <colyli@...as.com>
To: "Christoph Hellwig" <hch@...radead.org>
Cc: "Stephen Zhang" <starzhangzsd@...il.com>, <kent.overstreet@...ux.dev>, 
	<axboe@...nel.dk>, <sashal@...nel.org>, <linux-bcache@...r.kernel.org>, 
	<linux-kernel@...r.kernel.org>, <zhangshida@...inos.cn>
Subject: Re: [PATCH] bcache: fix double bio_endio completion in detached_dev_end_io

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