From: Matthew Brost <matthew.brost@intel.com>
To: Changyul Lee <lcy8047@gmail.com>
Cc: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Himal Prasad Ghimiray" <himal.prasad.ghimiray@intel.com>,
intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/xe: Release the SVM prefetch ranges of unparsed ops
Date: Fri, 13 Nov 2026 07:46:53 -0800 [thread overview]
Message-ID: <avcw7dxdP17Hw2x+@gsse-cloud1.jf.intel.com> (raw)
In-Reply-To: <20261113044239.2185984-1-lcy8047@gmail.com>
On Thu, Nov 12, 2026 at 11:42:39PM -0500, Changyul Lee wrote:
> vm_bind_ioctl_ops_create() stores SVM ranges, each with a reference, in
> op->prefetch_range.range for every PREFETCH op on a CPU address mirror
> VMA. xe_vma_ops_fini() releases them only for the ops on vops->list.
> When vm_bind_ioctl_ops_parse() fails, the ops after the failing one are
> never added to that list, and xe_vm_bind_ioctl() frees them with
> drm_gpuva_ops_free(), leaking their XArray nodes and range references.
> A PREFETCH that covers a userptr VMA and a CPU address mirror VMA after
> it does this when pinning the userptr pages fails.
>
> Release the prefetch ranges of all ops before freeing them. Ranges
> already released through vops->list leave an empty XArray, which
> xe_vma_svm_prefetch_ranges_fini() skips.
>
I believe I see the potential problem. I think this is right and safe
assuming xa_destroy is safe to be called twice which is appears to be.
Our CI will give use definitive answer which I have triggered your
behalf.
With that:
Reviewed-by: Matthew Brost <matthew.brost@intel.com>
> Fixes: 09ba0a8f06cd ("drm/xe/svm: Implement prefetch support for SVM ranges")
> Signed-off-by: Changyul Lee <lcy8047@gmail.com>
> ---
> Found with a static analysis tool we are developing.
>
> Compile-tested only, with x86_64_defconfig plus DRM_XE, DRM_XE_GPUSVM
> and W=1.
>
> drivers/gpu/drm/xe/xe_vm.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_vm.c b/drivers/gpu/drm/xe/xe_vm.c
> index d25de5652767..ee35ead79371 100644
> --- a/drivers/gpu/drm/xe/xe_vm.c
> +++ b/drivers/gpu/drm/xe/xe_vm.c
> @@ -4208,8 +4208,10 @@ int xe_vm_bind_ioctl(struct drm_device *dev, void *data, struct drm_file *file)
> vm_bind_ioctl_ops_unwind(vm, ops, args->num_binds);
> xe_vma_ops_fini(&vops);
> for (i = args->num_binds - 1; i >= 0; --i)
> - if (ops[i])
> + if (ops[i]) {
> + xe_svm_prefetch_gpuva_ops_fini(ops[i]);
> drm_gpuva_ops_free(&vm->gpuvm, ops[i]);
> + }
> free_syncs:
> if (err == -ENODATA)
> err = vm_bind_ioctl_signal_fences(vm, q, syncs, num_syncs);
>
> base-commit: 7475ea8b58616b33c04afb976cf0fbaad9dd63fb
> --
> 2.43.0
>
next prev parent reply other threads:[~2026-11-13 15:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 4:42 [PATCH] drm/xe: Release the SVM prefetch ranges of unparsed ops Changyul Lee
2026-11-13 4:57 ` sashiko-bot
2026-11-13 15:11 ` ✗ LGCI.VerificationFailed: failure for " Patchwork
2026-11-13 15:46 ` Matthew Brost [this message]
2026-11-13 16:01 ` ✓ CI.KUnit: success for drm/xe: Release the SVM prefetch ranges of unparsed ops (rev2) Patchwork
2026-11-13 16:33 ` ✓ Xe.CI.BAT: " Patchwork
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=avcw7dxdP17Hw2x+@gsse-cloud1.jf.intel.com \
--to=matthew.brost@intel.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=himal.prasad.ghimiray@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lcy8047@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=simona@ffwll.ch \
--cc=thomas.hellstrom@linux.intel.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