From: sashiko-bot@kernel.org
To: "Arvind Yadav" <arvind.yadav@intel.com>, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v2 1/3] CI_ONLY: Hold a device reference across deferred VM
Date: Fri, 13 Nov 2026 07:48:54 +0000 [thread overview]
Message-ID: <sashiko-outbox-212369@kernel.org> (raw)
In-Reply-To: <20261113073549.352746-2-arvind.yadav@intel.com>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] drm/xe: missing Fixes trailer and truncated CI_ONLY commit
subject
--
commit 5dc8382fd711cc6e72eaaab388a621fd70e80c06
Author: Arvind Yadav <arvind.yadav@intel.com>
> CI_ONLY: Hold a device reference across deferred VM
>
> xe_vm_free() queues vm_destroy_work_func() and returns.
> drm_gpuvm_free() then drops its device reference, but the worker
> still accesses device state while finishing VM destruction.
>
> Take a device reference before queueing the work and release it
> after the worker has finished using the device.
>
> Run the worker on the module-lifetime destroy workqueue. Releasing
> the last device reference can call xe_device_destroy(), which drains
> xe->destroy_wq. Running on that per-device workqueue would make the
> worker wait for itself.
>
> v3:
> - Move final VM destruction to the module-lifetime destroy workqueue
> in this patch to avoid self-deadlock on the last device put. (Sashiko)
>
> Signed-off-by: Arvind Yadav <arvind.yadav@intel.com>
[Severity: Low]
Since this fixes a device-lifetime bug in deferred teardown, should the
commit message include a Fixes tag?
Fixes: 61e18525023a ("drm/xe: Route deferred xe_vma/xe_vm teardown off system_dfl_wq")
Also, the subject line still carries a test prefix instead of "drm/xe:" and
is cut off at the end.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261113073549.352746-1-arvind.yadav@intel.com?part=1
next prev parent reply other threads:[~2026-11-13 7:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 7:35 [PATCH v2 0/3] CI-ONLY Fix VM teardown and migration queue recovery Arvind Yadav
2026-11-13 7:35 ` [PATCH v2 1/3] CI_ONLY: Hold a device reference across deferred VM Arvind Yadav
2026-11-13 7:48 ` sashiko-bot [this message]
2026-11-13 7:35 ` [PATCH v2 2/3] CI_ONLY Mark VMs as closing before queue cleanup Arvind Yadav
2026-11-13 7:51 ` sashiko-bot
2026-11-13 7:35 ` [PATCH v2 3/3] CI-ONLY:Defer VM teardown until exec " Arvind Yadav
2026-11-13 8:32 ` sashiko-bot
2026-11-13 7:43 ` ✗ CI.checkpatch: warning for CI-ONLY Fix VM teardown and migration queue recovery (rev2) Patchwork
2026-11-13 7:45 ` ✓ CI.KUnit: success " Patchwork
2026-11-13 8:16 ` ✓ 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=sashiko-outbox-212369@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=arvind.yadav@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=sashiko-reviews@lists.linux.dev \
/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.