From: Brajesh Gupta <Brajesh.Gupta@imgtec.com>
To: Luigi Santivetti <Luigi.Santivetti@imgtec.com>,
"tzimmermann@suse.de" <tzimmermann@suse.de>,
"simona@ffwll.ch" <simona@ffwll.ch>,
"airlied@gmail.com" <airlied@gmail.com>,
Alessio Belle <Alessio.Belle@imgtec.com>,
"maarten.lankhorst@linux.intel.com"
<maarten.lankhorst@linux.intel.com>,
"mripard@kernel.org" <mripard@kernel.org>,
"gye976@gmail.com" <gye976@gmail.com>
Cc: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"imagination@lists.freedesktop.org"
<imagination@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] drm/imagination: Fix reference and vm_bo handling in remap()
Date: Mon, 28 Sep 2026 09:10:02 +0000 [thread overview]
Message-ID: <8c182c4d6e9679a464cb29336c4000515e456ace.camel@imgtec.com> (raw)
In-Reply-To: <20260927-pvr-fixes-a-v1-1-7f5b18ab989a@gmail.com>
On Sun, 2026-09-27 at 17:25 +0900, Gyeyoung Baek wrote:
Hi Gyeyoung,
> When a map overlaps part of an existing mapping, pvr_vm_gpuva_remap()
> splits the mapping into prev/next parts covering what the request did
> not take, instead of creating something new. It gets two things wrong.
>
> - A GEM reference is taken for each part but it's never needed and never
> dropped, so it leaks one reference per split (remap-next-in-2m in
> tests/imagination/pvr_vm_map.c):
>
> CRITICAL: 33558528 bytes of shmem still held after close
>
> - The parts still belong to the original object being split, but
> pvr_vm_gpuva_remap() links them to ctx->gpuvm_bo, the new object's
> vm_bo:
>
> prev_va --obj--> BO_A BO_B <--obj-- vm_bo (ctx->gpuvm_bo)
> \___________link___________/ (mismatch: BO_A != BO_B)
>
> drm_gpuva_link() catches the mismatch:
>
> WARNING: drivers/gpu/drm/drm_gpuvm.c:2108 at drm_gpuva_link+0x2ec/0x310
> drm_WARN_ON(obj != vm_bo->obj)
> Call trace:
> drm_gpuva_link
> pvr_vm_gpuva_remap
> __drm_gpuvm_sm_map
> pvr_vm_map
> pvr_ioctl_vm_map
>
> Link them to op->remap.unmap->va->vm_bo instead.
>
> The locking of the GPUVA lists of the other objects touched by a split is
> not addressed here; it is handled by switching the GPUVM to immediate
> mode.
>
> Fixes: ff5f643de0bf ("drm/imagination: Add GEM and VM related code")
> Signed-off-by: Gyeyoung Baek <gye976@gmail.com>
Reviewed-by: Brajesh Gupta <brajesh.gupta@imgtec.com>
Thanks,
Brajesh
> ---
> drivers/gpu/drm/imagination/pvr_vm.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/imagination/pvr_vm.c b/drivers/gpu/drm/imagination/pvr_vm.c
> index ceb78694cd9..c5ae0b79fe6 100644
> --- a/drivers/gpu/drm/imagination/pvr_vm.c
> +++ b/drivers/gpu/drm/imagination/pvr_vm.c
> @@ -418,6 +418,8 @@ pvr_vm_gpuva_unmap(struct drm_gpuva_op *op, void *op_ctx)
> static int
> pvr_vm_gpuva_remap(struct drm_gpuva_op *op, void *op_ctx)
> {
> + /* The split parts belong to the object of the mapping being split. */
> + struct drm_gpuvm_bo *vm_bo = op->remap.unmap->va->vm_bo;
> struct pvr_vm_bind_op *ctx = op_ctx;
> u64 va_start = 0, va_range = 0;
> int err;
> @@ -433,14 +435,12 @@ pvr_vm_gpuva_remap(struct drm_gpuva_op *op, void *op_ctx)
> drm_gpuva_remap(&ctx->prev_va->base, &ctx->next_va->base, &op->remap);
>
> if (op->remap.prev) {
> - pvr_gem_object_get(gem_to_pvr_gem(ctx->prev_va->base.gem.obj));
> - drm_gpuva_link(&ctx->prev_va->base, ctx->gpuvm_bo);
> + drm_gpuva_link(&ctx->prev_va->base, vm_bo);
> ctx->prev_va = NULL;
> }
>
> if (op->remap.next) {
> - pvr_gem_object_get(gem_to_pvr_gem(ctx->next_va->base.gem.obj));
> - drm_gpuva_link(&ctx->next_va->base, ctx->gpuvm_bo);
> + drm_gpuva_link(&ctx->next_va->base, vm_bo);
> ctx->next_va = NULL;
> }
>
>
next prev parent reply other threads:[~2026-09-28 9:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-27 8:25 [PATCH 0/3] drm/imagination: Fix pre-existing bugs flagged by Sashiko's review of a VM_BIND series Gyeyoung Baek
2026-09-27 8:25 ` [PATCH 1/3] drm/imagination: Fix reference and vm_bo handling in remap() Gyeyoung Baek
2026-09-28 9:10 ` Brajesh Gupta [this message]
2026-09-27 8:25 ` [PATCH 2/3] drm/imagination: Fix pvr_mmu_map_sgl() overwriting its own error Gyeyoung Baek
2026-09-28 9:01 ` Brajesh Gupta
2026-09-28 9:19 ` Gyeyoung Baek
2026-09-27 8:25 ` [PATCH 3/3] drm/imagination: Size page table preallocation by device address Gyeyoung Baek
2026-09-28 9:03 ` Brajesh Gupta
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=8c182c4d6e9679a464cb29336c4000515e456ace.camel@imgtec.com \
--to=brajesh.gupta@imgtec.com \
--cc=Alessio.Belle@imgtec.com \
--cc=Luigi.Santivetti@imgtec.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gye976@gmail.com \
--cc=imagination@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--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 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®