From: sashiko-bot@kernel.org
To: "Michael J. Ruhl" <michael.j.ruhl@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v5 06/18] drm/xe/vsec: Do not register BMG PMT for VF
Date: Thu, 03 Sep 2026 20:33:59 +0000 [thread overview]
Message-ID: <20260903203359.B835F1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260903201002.1064889-26-michael.j.ruhl@intel.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Critical] Removing the `!xe->soc_remapper.set_telem_region` check introduces a NULL pointer dereference during PMT telemetry reads when the device is in boot survivability mode.
--
commit e9ec971f3f576a6d5f7a1224c18c5b1a5428ab39
Author: Michael J. Ruhl <michael.j.ruhl@intel.com>
drm/xe/vsec: Do not register BMG PMT for VF
This commit disables BMG PMT registration for Virtual Function (VF) nodes by
adding SR-IOV checks. It also removes the soc_remapper pointer check in the
telemetry read path.
> diff --git a/drivers/gpu/drm/xe/xe_vsec.c b/drivers/gpu/drm/xe/xe_vsec.c
> index a9baf0bfe572c..71bc359b2ad14 100644
> --- a/drivers/gpu/drm/xe/xe_vsec.c
> +++ b/drivers/gpu/drm/xe/xe_vsec.c
[ ... ]
> @@ -157,9 +160,6 @@ int xe_pmt_telem_read(struct device *dev, u32 guid, u64 *data, loff_t user_offse
>
> guard(mutex)(&xe->pmt.lock);
>
> - if (!xe->soc_remapper.set_telem_region)
> - return -ENODEV;
> -
[Severity: Critical]
Does removing this check introduce a NULL pointer dereference during PMT
telemetry reads when the device is in boot survivability mode?
If the device enters boot survivability mode (e.g., due to pcode failure or
configfs), xe_pci_probe() returns early. This skips xe_device_probe() and
xe_soc_remapper_init(), leaving xe->soc_remapper.set_telem_region as NULL.
However, xe_vsec_init() still registers the PMT capabilities during boot
survivability mode, exposing them via sysfs. Because the PCI core leaves
the device's runtime PM state as RPM_ACTIVE, a userspace read of the PMT
sysfs entry will bypass the xe_pm_runtime_get_if_active() check and
unconditionally dereference the NULL set_telem_region pointer later in this
function:
drivers/gpu/drm/xe/xe_vsec.c:xe_pmt_telem_read() {
...
/* Unconditional dereference of set_telem_region */
xe->soc_remapper.set_telem_region(xe, mem_region);
...
}
> /* indicate that we are not at an appropriate power level */
> if (!xe_pm_runtime_get_if_active(xe))
> return -ENODATA;
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260903201002.1064889-20-michael.j.ruhl@intel.com?part=6
next prev parent reply other threads:[~2026-09-03 20:34 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 20:10 [PATCH v5 00/18] Crescent Island PMT support Michael J. Ruhl
2026-09-03 20:10 ` [PATCH v5 01/18] platform/x86/intel/pmt: complete pcidev to device update Michael J. Ruhl
2026-09-03 20:27 ` sashiko-bot
2026-09-03 20:10 ` [PATCH v5 02/18] platform/x86/intel/pmt: refactor rmw with a return value Michael J. Ruhl
2026-09-03 20:10 ` [PATCH v5 03/18] platform/x86/intel/pmt: refactor rc " Michael J. Ruhl
2026-09-03 20:19 ` sashiko-bot
2026-09-03 20:33 ` Ruhl, Michael J
2026-09-03 20:10 ` [PATCH v5 04/18] platform/x86/intel/pmt: Add register access callbacks Michael J. Ruhl
2026-09-03 20:10 ` [PATCH v5 05/18] platform/x86/intel/pmt: Do not remap when using callbacks Michael J. Ruhl
2026-09-03 20:24 ` sashiko-bot
2026-09-03 20:54 ` Ruhl, Michael J
2026-09-03 20:10 ` [PATCH v5 06/18] drm/xe/vsec: Do not register BMG PMT for VF Michael J. Ruhl
2026-09-03 20:33 ` sashiko-bot [this message]
2026-09-03 20:10 ` [PATCH v5 07/18] drm/xe/vsec: Correct locking order Michael J. Ruhl
2026-09-03 20:10 ` [PATCH v5 08/18] drm/xe/vsec: Use correct pm state get Michael J. Ruhl
2026-09-03 20:26 ` sashiko-bot
2026-09-03 20:55 ` Ruhl, Michael J
2026-09-03 20:10 ` [PATCH v5 09/18] drm/xe/vsec: Add DOC text for VSEC Michael J. Ruhl
2026-09-03 20:17 ` sashiko-bot
2026-09-03 20:34 ` Ruhl, Michael J
2026-09-03 20:10 ` [PATCH v5 10/18] drm/xe/vsec: Support possible hotplug exit Michael J. Ruhl
2026-09-03 20:10 ` [PATCH v5 11/18] drm/xe/vsec: Support Crescent Island PMT Michael J. Ruhl
2026-09-03 20:10 ` [PATCH v5 12/18] drm/xe/vsec: Refactor BattleMage PMT defines Michael J. Ruhl
2026-09-03 20:10 ` [PATCH v5 13/18] drm/xe/vsec: Crescent Island PMT decode Michael J. Ruhl
2026-09-03 20:10 ` [PATCH v5 14/18] drm/xe/vsec: Crescent Island PMT callbacks Michael J. Ruhl
2026-09-03 20:26 ` sashiko-bot
2026-09-03 20:10 ` [PATCH v5 15/18] drm/xe/vsec: Support late bind fw information Michael J. Ruhl
2026-09-03 20:28 ` sashiko-bot
2026-09-03 20:57 ` Ruhl, Michael J
2026-09-03 20:10 ` [PATCH v5 16/18] drm/xe/vsec: Add PMT GUID internal access Michael J. Ruhl
2026-09-04 15:14 ` Poosa, Karthik
2026-09-04 16:00 ` Ruhl, Michael J
2026-09-03 20:10 ` [PATCH v5 17/18] drm/xe/vsec: Update PMT " Michael J. Ruhl
2026-09-03 20:10 ` [PATCH v5 18/18] drm/xe/vsec: Refactor platform check Michael J. Ruhl
2026-09-03 20:17 ` ✗ CI.checkpatch: warning for Crescent Island PMT support (rev7) Patchwork
2026-09-03 20:18 ` ✗ CI.KUnit: failure " 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=20260903203359.B835F1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=michael.j.ruhl@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox