From: Zhihao Cheng <chengzhihao1@huawei.com>
To: <agk@redhat.com>, <snitzer@kernel.org>, <mpatocka@redhat.com>,
<bmarzins@redhat.com>
Cc: <dm-devel@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
<yangerkun@huawei.com>, <lilingfeng3@huawei.com>
Subject: Re: [PATCH] dm: pass origin bio's bdev to bio_alloc_clone
Date: Fri, 23 Jan 2026 09:12:53 +0800 [thread overview]
Message-ID: <bb49f820-473a-a951-60b0-32dcd8fb0110@huawei.com> (raw)
In-Reply-To: <20260116120744.908987-1-chengzhihao1@huawei.com>
在 2026/1/16 20:07, Zhihao Cheng 写道:
friendly ping
> The origin bio carries blk-cgroup information which could be set from
> foreground(task_css(css) - wbc->wb->blkcg_css), so the blkcg won't
> control buffer io since commit ca522482e3eaf ("dm: pass NULL bdev to
> bio_alloc_clone"). The synchronous io is still under control by blkcg,
> because 'bio->bi_blkg' is set by io submitting task which has been
> added into 'cgroup.procs'.
>
> Fix it by passing origin bio's bdev to bio_alloc_clone.
>
> Fetch a reproducer in [Link].
>
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=220985
> Fixes: ca522482e3eaf ("dm: pass NULL bdev to bio_alloc_clone")
> Signed-off-by: Zhihao Cheng <chengzhihao1@huawei.com>
> ---
> drivers/md/dm.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/md/dm.c b/drivers/md/dm.c
> index b63279202260..e763e3b02a9f 100644
> --- a/drivers/md/dm.c
> +++ b/drivers/md/dm.c
> @@ -574,7 +574,8 @@ static struct dm_io *alloc_io(struct mapped_device *md, struct bio *bio, gfp_t g
> struct dm_target_io *tio;
> struct bio *clone;
>
> - clone = bio_alloc_clone(NULL, bio, gfp_mask, &md->mempools->io_bs);
> + clone = bio_alloc_clone(bio->bi_bdev, bio,
> + gfp_mask, &md->mempools->io_bs);
> if (unlikely(!clone))
> return NULL;
> tio = clone_to_tio(clone);
> @@ -623,7 +624,7 @@ static struct bio *alloc_tio(struct clone_info *ci, struct dm_target *ti,
> /* alloc_io() already initialized embedded clone */
> clone = &tio->clone;
> } else {
> - clone = bio_alloc_clone(NULL, ci->bio, gfp_mask,
> + clone = bio_alloc_clone(ci->bio->bi_bdev, ci->bio, gfp_mask,
> &md->mempools->bs);
> if (!clone)
> return NULL;
>
next prev parent reply other threads:[~2026-01-23 1:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 12:07 Zhihao Cheng
2026-01-23 1:12 ` Zhihao Cheng [this message]
2026-01-23 16:16 ` Mikulas Patocka
2026-01-24 7:23 ` Zhihao Cheng
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=bb49f820-473a-a951-60b0-32dcd8fb0110@huawei.com \
--to=chengzhihao1@huawei.com \
--cc=agk@redhat.com \
--cc=bmarzins@redhat.com \
--cc=dm-devel@lists.linux.dev \
--cc=lilingfeng3@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=snitzer@kernel.org \
--cc=yangerkun@huawei.com \
/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®