From: Boris Brezillon <boris.brezillon@collabora.com>
To: Akash Goel <akash.goel@arm.com>
Cc: liviu.dudau@arm.com, steven.price@arm.com,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, airlied@gmail.com, daniel@ffwll.ch,
nd@arm.com
Subject: Re: [PATCH v2] drm/panthor: Fix potential memleak of vma structure
Date: Tue, 21 Oct 2025 09:41:25 +0200 [thread overview]
Message-ID: <20251021094125.7be19764@fedora> (raw)
In-Reply-To: <20251020200243.1324045-1-akash.goel@arm.com>
On Mon, 20 Oct 2025 21:02:43 +0100
Akash Goel <akash.goel@arm.com> wrote:
> This commit addresses a memleak issue of panthor_vma (or drm_gpuva)
> structure in Panthor driver, that can happen if the GPU page table
> update operation to map the pages fail.
> The issue is very unlikely to occur in practice.
>
> v2: Add panthor_vm_op_ctx_return_vma() helper (Boris)
>
> Fixes: 647810ec2476 ("drm/panthor: Add the MMU/VM logical block")
> Signed-off-by: Akash Goel <akash.goel@arm.com>
Just one minor thing below, but the patch is
Reviewed-by: Boris Brezillon <boris.brezillon@collabora.com>
regardless.
> ---
> drivers/gpu/drm/panthor/panthor_mmu.c | 16 +++++++++++++++-
> 1 file changed, 15 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/panthor/panthor_mmu.c b/drivers/gpu/drm/panthor/panthor_mmu.c
> index 6dec4354e378..63af8ee89b08 100644
> --- a/drivers/gpu/drm/panthor/panthor_mmu.c
> +++ b/drivers/gpu/drm/panthor/panthor_mmu.c
> @@ -1146,6 +1146,18 @@ static void panthor_vm_cleanup_op_ctx(struct panthor_vm_op_ctx *op_ctx,
> }
> }
>
> +static void
> +panthor_vm_op_ctx_return_vma(struct panthor_vm_op_ctx *op_ctx,
> + struct panthor_vma *vma)
> +{
> + for (u32 i = 0; i < ARRAY_SIZE(op_ctx->preallocated_vmas); i++) {
> + if (!op_ctx->preallocated_vmas[i]) {
> + op_ctx->preallocated_vmas[i] = vma;
> + return;
> + }
> + }
Maybe add a WARN_ON_ONCE() here.
> +}
> +
> static struct panthor_vma *
> panthor_vm_op_ctx_get_vma(struct panthor_vm_op_ctx *op_ctx)
> {
> @@ -2081,8 +2093,10 @@ static int panthor_gpuva_sm_step_map(struct drm_gpuva_op *op, void *priv)
> ret = panthor_vm_map_pages(vm, op->map.va.addr, flags_to_prot(vma->flags),
> op_ctx->map.sgt, op->map.gem.offset,
> op->map.va.range);
> - if (ret)
> + if (ret) {
> + panthor_vm_op_ctx_return_vma(op_ctx, vma);
> return ret;
> + }
>
> /* Ref owned by the mapping now, clear the obj field so we don't release the
> * pinning/obj ref behind GPUVA's back.
prev parent reply other threads:[~2025-10-21 7:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 20:02 [PATCH v2] drm/panthor: Fix potential memleak of vma structure Akash Goel
2025-10-20 21:59 ` Liviu Dudau
2025-10-21 7:41 ` Boris Brezillon [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=20251021094125.7be19764@fedora \
--to=boris.brezillon@collabora.com \
--cc=airlied@gmail.com \
--cc=akash.goel@arm.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=nd@arm.com \
--cc=steven.price@arm.com \
--cc=tzimmermann@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.