From: Jani Nikula <jani.nikula@linux.intel.com>
To: Eugene Kobyak <eugene.kobyak@intel.com>, intel-gfx@lists.freedesktop.org
Cc: John.C.Harrison@intel.com, andi.shyti@linux.intel.com
Subject: Re: [PATCH v5] drm/i915: Fix NULL pointer dereference in capture_engine
Date: Tue, 03 Dec 2024 14:27:34 +0200 [thread overview]
Message-ID: <87mshd3qa1.fsf@intel.com> (raw)
In-Reply-To: <4yfdzisxkb3j3tig2astee5zd46ppt2jwhqffkhes2dwm3g5nb@snadyfwzl7g4>
On Tue, 03 Dec 2024, Eugene Kobyak <eugene.kobyak@intel.com> wrote:
> When the intel_context structure contains NULL,
> it raises a NULL pointer dereference error in drm_info().
Blank line here between commit message body and trailers.
> Fixes: e8a3319c31a1 ("drm/i915: Allow error capture without a request")
> Closes: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/12309
> Cc: John Harrison <John.C.Harrison@Intel.com>
> Cc: <stable@vger.kernel.org> # v6.3+
> Signed-off-by: Eugene Kobyak <eugene.kobyak@intel.com>
> ---
> v2:
> - return drm_info to separate condition
> v3:
> - create separate condition which generate string if intel_context exist
> v4:
> - rollback and add check intel_context in log condition
> v5:
> - create separate string with guc_id if intel_context exist
> drivers/gpu/drm/i915/i915_gpu_error.c | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_gpu_error.c b/drivers/gpu/drm/i915/i915_gpu_error.c
> index 135ded17334e..4ca6b9872a48 100644
> --- a/drivers/gpu/drm/i915/i915_gpu_error.c
> +++ b/drivers/gpu/drm/i915/i915_gpu_error.c
> @@ -1643,9 +1643,12 @@ capture_engine(struct intel_engine_cs *engine,
> return NULL;
>
> intel_engine_get_hung_entity(engine, &ce, &rq);
> - if (rq && !i915_request_started(rq))
> - drm_info(&engine->gt->i915->drm, "Got hung context on %s with active request %lld:%lld [0x%04X] not yet started\n",
> - engine->name, rq->fence.context, rq->fence.seqno, ce->guc_id.id);
> + if (rq && !i915_request_started(rq)) {
> + char guc_id[11];
> + ce ? snprintf(guc_id, sizeof(guc_id), " [0x%04x] ", ce->guc_id.id) : snprintf(guc_id, sizeof(guc_id), " ");
I don't know if there's a separate coding style entry saying you
shouldn't use a ternary operator like that, but you shouldn't use a
ternary operator like that.
BR,
Jani.
> + drm_info(&engine->gt->i915->drm, "Got hung context on %s with active request %lld:%lld%snot yet started\n",
> + engine->name, rq->fence.context, rq->fence.seqno, guc_id);
> + }
>
> if (rq) {
> capture = intel_engine_coredump_add_request(ee, rq, ATOMIC_MAYFAIL);
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-12-03 12:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 11:59 [PATCH v5] drm/i915: Fix NULL pointer dereference in capture_engine Eugene Kobyak
2024-12-03 12:27 ` Jani Nikula [this message]
2024-12-03 12:33 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Fix NULL pointer dereference in capture_engine (rev2) Patchwork
2024-12-03 12:59 ` ✓ i915.CI.BAT: success " Patchwork
2024-12-03 13:14 ` [PATCH v5] drm/i915: Fix NULL pointer dereference in capture_engine Andi Shyti
2024-12-03 14:40 ` ✓ i915.CI.Full: success for drm/i915: Fix NULL pointer dereference in capture_engine (rev2) 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=87mshd3qa1.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=John.C.Harrison@intel.com \
--cc=andi.shyti@linux.intel.com \
--cc=eugene.kobyak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
/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.