From: "Michael J. Ruhl" <michael.j.ruhl@intel.com>
To: platform-driver-x86@vger.kernel.org,
intel-xe@lists.freedesktop.org, hdegoede@redhat.com,
ilpo.jarvinen@linux.intel.com, lucas.demarchi@intel.com,
rodrigo.vivi@intel.com
Cc: "Michael J. Ruhl" <michael.j.ruhl@intel.com>
Subject: [PATCH v2 5/8] platform/x86/intel/pmt: crashlog binary file endpoint
Date: Fri, 30 May 2025 16:37:54 -0400 [thread overview]
Message-ID: <20250530203757.190853-6-michael.j.ruhl@intel.com> (raw)
In-Reply-To: <20250530203757.190853-1-michael.j.ruhl@intel.com>
Usage of the intel_pmt_read() for binary sysfs, requires an
allocated endpoint struct. The crashlog driver does not
allocate the endpoint.
Without the ep, the crashlog usage causes the following NULL
pointer exception:
BUG: kernel NULL pointer dereference, address: 0000000000000000
Oops: Oops: 0000 [#1] SMP NOPTI
RIP: 0010:intel_pmt_read+0x3b/0x70 [pmt_class]
Code:
Call Trace:
<TASK>
? sysfs_kf_bin_read+0xc0/0xe0
kernfs_fop_read_iter+0xac/0x1a0
vfs_read+0x26d/0x350
ksys_read+0x6b/0xe0
__x64_sys_read+0x1d/0x30
x64_sys_call+0x1bc8/0x1d70
do_syscall_64+0x6d/0x110
Add the endpoint information to the crashlog driver to avoid
the NULL pointer exception.
Fixes: 416eeb2e1fc7 ("platform/x86/intel/pmt: telemetry: Export API to read telemetry")
Signed-off-by: Michael J. Ruhl <michael.j.ruhl@intel.com>
---
drivers/platform/x86/intel/pmt/crashlog.c | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/drivers/platform/x86/intel/pmt/crashlog.c b/drivers/platform/x86/intel/pmt/crashlog.c
index c6d8a7a61d39..94858bfb52f8 100644
--- a/drivers/platform/x86/intel/pmt/crashlog.c
+++ b/drivers/platform/x86/intel/pmt/crashlog.c
@@ -250,6 +250,7 @@ static struct intel_pmt_namespace pmt_crashlog_ns = {
.xa = &crashlog_array,
.attr_grp = &pmt_crashlog_group,
.pmt_header_decode = pmt_crashlog_header_decode,
+ .pmt_add_endpoint = intel_pmt_add_endpoint,
};
/*
@@ -260,8 +261,12 @@ static void pmt_crashlog_remove(struct auxiliary_device *auxdev)
struct pmt_crashlog_priv *priv = auxiliary_get_drvdata(auxdev);
int i;
- for (i = 0; i < priv->num_entries; i++)
- intel_pmt_dev_destroy(&priv->entry[i].entry, &pmt_crashlog_ns);
+ for (i = 0; i < priv->num_entries; i++) {
+ struct intel_pmt_entry *entry = &priv->entry[i].entry;
+
+ intel_pmt_release_endpoint(entry->ep);
+ intel_pmt_dev_destroy(entry, &pmt_crashlog_ns);
+ }
}
static int pmt_crashlog_probe(struct auxiliary_device *auxdev,
--
2.49.0
next prev parent reply other threads:[~2025-05-30 20:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-30 20:37 [PATCH v2 0/8] Crashlog Type1 Version2 support Michael J. Ruhl
2025-05-30 20:37 ` [PATCH v2 1/8] drm/xe: Correct BMG VSEC header sizing Michael J. Ruhl
2025-05-30 20:37 ` [PATCH v2 2/8] platform/x86/intel/pmt: white space cleanup Michael J. Ruhl
2025-05-30 20:37 ` [PATCH v2 3/8] platform/x86/intel/pmt: use guard(mutex) Michael J. Ruhl
2025-05-30 20:37 ` [PATCH v2 4/8] platform/x86/intel: refactor endpoint usage Michael J. Ruhl
2025-05-30 20:37 ` Michael J. Ruhl [this message]
2025-05-30 20:37 ` [PATCH v2 6/8] platform/x86/intel/pmt: decouple sysfs and namespace Michael J. Ruhl
2025-05-30 20:37 ` [PATCH v2 7/8] platform/x86/intel/pmt: use a version struct Michael J. Ruhl
2025-05-30 20:37 ` [PATCH v2 8/8] platform/x86/intel/pmt: support BMG crashlog Michael J. Ruhl
2025-05-30 20:43 ` ✓ CI.Patch_applied: success for Crashlog Type1 Version2 support (rev2) Patchwork
2025-05-30 20:44 ` ✓ CI.checkpatch: " Patchwork
2025-05-30 20:45 ` ✓ CI.KUnit: " Patchwork
2025-05-30 20:55 ` ✓ CI.Build: " Patchwork
2025-05-30 20:58 ` ✓ CI.Hooks: " Patchwork
2025-05-30 20:59 ` ✓ CI.checksparse: " Patchwork
2025-05-30 21:23 ` ✓ Xe.CI.BAT: " Patchwork
2025-06-01 14:21 ` ✗ Xe.CI.Full: 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=20250530203757.190853-6-michael.j.ruhl@intel.com \
--to=michael.j.ruhl@intel.com \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rodrigo.vivi@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