linux-kernel - Re: Fwd: [PATCH v3] bcache: use bio cloning for detached device requests

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <0a1bd601-7f66-428e-ae1a-4972f383258f@kernel.dk>
Date: Wed, 21 Jan 2026 19:22:44 -0700
From: Jens Axboe <axboe@...nel.dk>
To: Stephen Zhang <starzhangzsd@...il.com>
Cc: Coly Li <colyli@...as.com>, Kent Overstreet <kent.overstreet@...ux.dev>,
 Sasha Levin <sashal@...nel.org>, Christoph Hellwig <hch@...radead.org>,
 linux-bcache@...r.kernel.org,
 Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
 zhangshida <zhangshida@...inos.cn>
Subject: Re: Fwd: [PATCH v3] bcache: use bio cloning for detached device
 requests

On 1/21/26 7:20 PM, Stephen Zhang wrote:
> Jens Axboe <axboe@...nel.dk> 于2026年1月22日周四 10:08写道：
>>
>> On 1/21/26 6:40 PM, Stephen Zhang wrote:
>>> ---------- Forwarded message ---------
>>
>> Can you please just send it out as a regular patch? The forward has
>> complete whitespace damage (it's all spaces, no tabs), and when you
>> forward, b4 doesn't pick it up either. Maybe there's some reason for
>> why you are doing these as forwards, if so do tell?
>>
> 
> Apologies for the formatting issues with the forwarded patch. When I try
> using git send-email, I'm encountering server rejection issues.
> Interestingly, I found that if I cut the patch content in half, it goes
> through without rejection. This suggests there may be a size limit or
> specific content filter causing the problem.
> 
> I'm investigating which part triggers the rejection and will resend the
> patch properly once resolved.

Can you put it in a git tree? Your original patches seem to have been
applied by Coly just fine, so maybe just go that route again?

-- 
Jens Axboe