From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Shuicheng Lin" <shuicheng.lin@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: ✗ CI.checkpatch: warning for series starting with [1/1] drm/xe: Fix error cleanup in xe_exec_queue_create_ioctl() (rev2)
Date: Fri, 10 Apr 2026 03:18:23 -0000 [thread overview]
Message-ID: <177579110364.449057.7336473864425807945@a3b018990fe9> (raw)
In-Reply-To: <20260408020647.3397933-1-shuicheng.lin@intel.com>
== Series Details ==
Series: series starting with [1/1] drm/xe: Fix error cleanup in xe_exec_queue_create_ioctl() (rev2)
URL : https://patchwork.freedesktop.org/series/164483/
State : warning
== Summary ==
+ KERNEL=/kernel
+ git clone https://gitlab.freedesktop.org/drm/maintainer-tools mt
Cloning into 'mt'...
warning: redirecting to https://gitlab.freedesktop.org/drm/maintainer-tools.git/
+ git -C mt rev-list -n1 origin/master
1f57ba1afceae32108bd24770069f764d940a0e4
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 1249aa881479fc81bfbd25d0ae3cf7e897ca75ae
Author: Shuicheng Lin <shuicheng.lin@intel.com>
Date: Wed Apr 8 02:06:47 2026 +0000
drm/xe: Fix error cleanup in xe_exec_queue_create_ioctl()
Two error handling issues exist in xe_exec_queue_create_ioctl():
1. When xe_hw_engine_group_add_exec_queue() fails, the error path jumps
to put_exec_queue which skips xe_exec_queue_kill(). If the VM is in
preempt fence mode, xe_vm_add_compute_exec_queue() has already added
the queue to the VM's compute exec queue list. Skipping the kill
leaves the queue on that list, leading to a dangling pointer after
the queue is freed.
2. When xa_alloc() fails after xe_hw_engine_group_add_exec_queue() has
succeeded, the error path does not call
xe_hw_engine_group_del_exec_queue() to remove the queue from the hw
engine group list. The queue is then freed while still linked into
the hw engine group, causing a use-after-free.
Fix both by:
- Changing the xe_hw_engine_group_add_exec_queue() failure path to jump
to kill_exec_queue so that xe_exec_queue_kill() properly removes the
queue from the VM's compute list.
- Adding a del_hw_engine_group label before kill_exec_queue for the
xa_alloc() failure path, which removes the queue from the hw engine
group before proceeding with the rest of the cleanup.
Fixes: 7970cb36966c ("'drm/xe/hw_engine_group: Register hw engine group's exec queues")
Cc: Francois Dugast <francois.dugast@intel.com>
Cc: Matthew Brost <matthew.brost@intel.com>
Cc: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
Assisted-by: Claude:claude-opus-4.6
Signed-off-by: Shuicheng Lin <shuicheng.lin@intel.com>
Reviewed-by: Matthew Brost <matthew.brost@intel.com>
+ /mt/dim checkpatch 97d8833ffba6bd3d6aaa51169069620ac17a2e37 drm-intel
1249aa881479 drm/xe: Fix error cleanup in xe_exec_queue_create_ioctl()
-:33: WARNING:BAD_SIGN_OFF: Non-standard signature: Assisted-by:
#33:
Assisted-by: Claude:claude-opus-4.6
-:33: ERROR:BAD_SIGN_OFF: Unrecognized email address: 'Claude:claude-opus-4.6'
#33:
Assisted-by: Claude:claude-opus-4.6
total: 1 errors, 1 warnings, 0 checks, 24 lines checked
next prev parent reply other threads:[~2026-04-10 3:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 2:06 [PATCH 1/1] drm/xe: Fix error cleanup in xe_exec_queue_create_ioctl() Shuicheng Lin
2026-04-08 2:17 ` ✗ CI.checkpatch: warning for series starting with [1/1] " Patchwork
2026-04-08 2:18 ` ✗ CI.KUnit: failure " Patchwork
2026-04-08 4:48 ` [PATCH 1/1] " Matthew Brost
2026-04-10 3:18 ` Patchwork [this message]
2026-04-10 3:19 ` ✓ CI.KUnit: success for series starting with [1/1] drm/xe: Fix error cleanup in xe_exec_queue_create_ioctl() (rev2) Patchwork
2026-04-10 4:10 ` ✓ Xe.CI.BAT: " Patchwork
2026-04-10 9:13 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-04-14 15:47 ` Lin, Shuicheng
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=177579110364.449057.7336473864425807945@a3b018990fe9 \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=shuicheng.lin@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 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.