From: Jens Axboe <axboe@kernel.dk>
To: colyli@fnnas.com, kent.overstreet@linux.dev, hch@infradead.org,
zhangshida2026@163.com
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: Wed, 28 Jan 2026 19:07:20 -0700 [thread overview]
Message-ID: <176965244085.445345.14457521939729169467.b4-ty@kernel.dk> (raw)
In-Reply-To: <20260127082112.1114158-1-zhangshida2026@163.com>
On Tue, 27 Jan 2026 16:21:10 +0800, zhangshida2026@163.com wrote:
> 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.
>
> [...]
Applied, thanks!
[1/2] bcache: remove dead code in detached_dev_do_request
commit: 6ea84d7a92cb0b30aaf7d2066a69e28e27932332
[2/2] bcache: fix I/O accounting leak in detached_dev_do_request
commit: 4da7c5c3ec34d839bba6e035c3d05c447a2f9d4f
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2026-01-29 2:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 8:21 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 ` Re:[PATCH v3 0/2] bcache: fix I/O accounting leak zhangshida2026
2026-01-29 2:07 ` Jens Axboe [this message]
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=176965244085.445345.14457521939729169467.b4-ty@kernel.dk \
--to=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=zhangshida2026@163.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®