From: "Yu Kuai" <yukuai@fnnas.com>
To: "Abd-Alrhman Masalkhi" <abd.masalkhi@gmail.com>,
<song@kernel.org>, <linan666@huaweicloud.com>
Cc: <linux-raid@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<yukuai@fnnas.com>
Subject: Re: [PATCH v2] md: use md_free_cloned_bio() in md_end_clone_io()
Date: Sun, 19 Apr 2026 12:51:29 +0800 [thread overview]
Message-ID: <36f8b219-140d-4d66-85f9-2522215f5a2b@fnnas.com> (raw)
In-Reply-To: <20260415081941.352389-1-abd.masalkhi@gmail.com>
Hi,
在 2026/4/15 16:19, Abd-Alrhman Masalkhi 写道:
> md_end_clone_io() and md_free_cloned_bio() share identical teardown
> logic. Use md_free_cloned_bio() in md_end_clone_io() for cleanup and
> call bio_endio() afterwards.
>
> Signed-off-by: Abd-Alrhman Masalkhi <abd.masalkhi@gmail.com>
> ---
> Changes in v2:
> - Reuse md_free_cloned_bio() instead of introducing a new helper
> - Link to v1: https://lore.kernel.org/linux-raid/20260414103813.307601-1-abd.masalkhi@gmail.com
> ---
> drivers/md/md.c | 13 +------------
> 1 file changed, 1 insertion(+), 12 deletions(-)
>
> diff --git a/drivers/md/md.c b/drivers/md/md.c
> index ac71640ff3a8..8565566a447b 100644
> --- a/drivers/md/md.c
> +++ b/drivers/md/md.c
> @@ -9212,20 +9212,9 @@ static void md_end_clone_io(struct bio *bio)
> {
> struct md_io_clone *md_io_clone = bio->bi_private;
> struct bio *orig_bio = md_io_clone->orig_bio;
> - struct mddev *mddev = md_io_clone->mddev;
> -
> - if (bio_data_dir(orig_bio) == WRITE && md_bitmap_enabled(mddev, false))
> - md_bitmap_end(mddev, md_io_clone);
> -
> - if (bio->bi_status && !orig_bio->bi_status)
> - orig_bio->bi_status = bio->bi_status;
> -
> - if (md_io_clone->start_time)
> - bio_end_io_acct(orig_bio, md_io_clone->start_time);
>
> - bio_put(bio);
> + md_free_cloned_bio(bio);
> bio_endio(orig_bio);
> - percpu_ref_put(&mddev->active_io);
> }
>
> static void md_clone_bio(struct mddev *mddev, struct bio **bio)
Same as I replied to v1,
This patch is no longer needed after following patch:
https://lore.kernel.org/r/20260408043548.1695157-1-bmarzins@redhat.com
--
Thansk,
Kuai
next prev parent reply other threads:[~2026-04-19 4:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 8:19 [PATCH v2] md: use md_free_cloned_bio() in md_end_clone_io() Abd-Alrhman Masalkhi
2026-04-16 6:47 ` Li Nan
2026-04-16 7:39 ` Abd-Alrhman Masalkhi
2026-04-17 1:29 ` Li Nan
2026-04-19 4:51 ` Yu Kuai [this message]
2026-04-20 7:34 ` Abd-Alrhman Masalkhi
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=36f8b219-140d-4d66-85f9-2522215f5a2b@fnnas.com \
--to=yukuai@fnnas.com \
--cc=abd.masalkhi@gmail.com \
--cc=linan666@huaweicloud.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=song@kernel.org \
/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