mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: zhangshida2026  <zhangshida2026@163.com>
To: colyli@fnnas.com, kent.overstreet@linux.dev, hch@infradead.org,
	axboe@kernel.dk
Cc: linux-bcache@vger.kernel.org, linux-kernel@vger.kernel.org,
	zhangshida@kylinos.cn, starzhangzsd@gmail.com
Subject: Re:[PATCH v3 0/2] bcache: fix I/O accounting leak
Date: Thu, 29 Jan 2026 09:54:08 +0800 (CST)	[thread overview]
Message-ID: <4134f033.14c9.19c07753714.Coremail.zhangshida2026@163.com> (raw)
In-Reply-To: <20260127082112.1114158-1-zhangshida2026@163.com>


















At 2026-01-27 16:21:10, zhangshida2026@163.com wrote:
>From: Shida Zhang <zhangshida@kylinos.cn>
>
>This series addresses an I/O accounting leak where detached bcache
>devices could report 100% utilization in iostat after completion
>of discard requests.
>
>Changes since v2:
>- Omitting the dead NULL check for bio_alloc_clone() (suggested by hch).
>- Updated the Fixes tag for the accounting leak.
>
>Shida Zhang (2):
>  bcache: remove dead code in detached_dev_do_request
>  bcache: fix I/O accounting leak in detached_dev_do_request
>
> drivers/md/bcache/request.c | 6 +-----
> 1 file changed, 1 insertion(+), 5 deletions(-)

>


Hi Jens,

The patches have been reviewed by Christoph and acked by Coly. 
Given that we are now at rc7, I wanted to see if you would consider picking 
these up for the 6.19 cycle?

Thank you for your time and for all your work.

Best regards,
Shida Zhang

>-- 
>2.34.1

  parent reply	other threads:[~2026-01-29  1:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-27  8:21 [PATCH " zhangshida2026
2026-01-27  8:21 ` [PATCH v3 1/2] bcache: remove dead code in detached_dev_do_request zhangshida2026
2026-01-27  8:28   ` Christoph Hellwig
2026-01-27  8:21 ` [PATCH v3 2/2] bcache: fix I/O accounting leak " zhangshida2026
2026-01-27  8:29   ` Christoph Hellwig
2026-01-29  1:54 ` zhangshida2026 [this message]
2026-01-29  2:07 ` [PATCH v3 0/2] bcache: fix I/O accounting leak Jens Axboe

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=4134f033.14c9.19c07753714.Coremail.zhangshida2026@163.com \
    --to=zhangshida2026@163.com \
    --cc=axboe@kernel.dk \
    --cc=colyli@fnnas.com \
    --cc=hch@infradead.org \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-bcache@vger.kernel.org \
    --cc=linux-kernel@vger.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

all inboxes | Powered by JetHome®