From: Brett Creeley <bcreeley@amd.com>
To: Zilin Guan <zilin@seu.edu.cn>, jgg@ziepe.ca
Cc: yishaih@nvidia.com, shameerali.kolothum.thodi@huawei.com,
kevin.tian@intel.com, brett.creeley@amd.com,
alex.williamson@redhat.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, jianhao.xu@seu.edu.cn
Subject: Re: [PATCH V2] vfio/pds: replace bitmap_free with vfree
Date: Mon, 15 Sep 2025 09:28:47 -0700 [thread overview]
Message-ID: <85aa036a-7b67-483e-81d3-8809abcb4a33@amd.com> (raw)
In-Reply-To: <20250913153154.1028835-1-zilin@seu.edu.cn>
On 9/13/2025 8:31 AM, Zilin Guan wrote:
> Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.
>
>
> host_seq_bmp is allocated with vzalloc but is currently freed with
> bitmap_free, which uses kfree internally. This mismach prevents the
> resource from being released properly and may result in memory leaks
> or other issues.
>
> Fix this by freeing host_seq_bmp with vfree to match the vzalloc
> allocation.
>
> Fixes: f232836a9152 ("vfio/pds: Add support for dirty page tracking")
> Signed-off-by: Zilin Guan <zilin@seu.edu.cn>
> ---
>
> Changes in v2:
> - Fix the incorrect description in the commit log.
> - Add "Fixes" tag accordingly.
>
> drivers/vfio/pci/pds/dirty.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/vfio/pci/pds/dirty.c b/drivers/vfio/pci/pds/dirty.c
> index c51f5e4c3dd6..481992142f79 100644
> --- a/drivers/vfio/pci/pds/dirty.c
> +++ b/drivers/vfio/pci/pds/dirty.c
> @@ -82,7 +82,7 @@ static int pds_vfio_dirty_alloc_bitmaps(struct pds_vfio_region *region,
>
> host_ack_bmp = vzalloc(bytes);
> if (!host_ack_bmp) {
> - bitmap_free(host_seq_bmp);
> + vfree(host_seq_bmp);
Thanks for fixing this. I must have missed this from when the bitmap was
reworked.
Reviewed-by: Brett Creeley <brett.creeley@amd.com>
> return -ENOMEM;
> }
>
> --
> 2.34.1
>
prev parent reply other threads:[~2025-09-15 16:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-13 15:31 [PATCH V2] vfio/pds: replace bitmap_free with vfree Zilin Guan
2025-09-15 16:28 ` Brett Creeley [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=85aa036a-7b67-483e-81d3-8809abcb4a33@amd.com \
--to=bcreeley@amd.com \
--cc=alex.williamson@redhat.com \
--cc=brett.creeley@amd.com \
--cc=jgg@ziepe.ca \
--cc=jianhao.xu@seu.edu.cn \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=yishaih@nvidia.com \
--cc=zilin@seu.edu.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