Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 v3] drm/i915: Fixed NULL pointer dereference in capture_engine
Date: Thu, 28 Nov 2024 14:57:46 +0200	[thread overview]
Message-ID: <874j3r8qid.fsf@intel.com> (raw)
In-Reply-To: <etwgucaj4hu7buvrvzgxkhxjtl526qd6fdyfmxzsdacphrg667@nrd35hese3t5>

On Mon, 25 Nov 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().
>
> Fixes: e8a3319c31a1 ("drm/i915: Allow error capture without a request")
> Closes: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/12309
>

Superfluous newline in the middle of commit trailers.

Please use the imperative mood in the subject, i.e. s/Fixed/Fix/.

BR,
Jani.

> Signed-off-by: Eugene Kobyak <eugene.kobyak@intel.com>
> ---
>  drivers/gpu/drm/i915/i915_gpu_error.c | 13 ++++++++++---
>  1 file changed, 10 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..1c614c74c2cf 100644
> --- a/drivers/gpu/drm/i915/i915_gpu_error.c
> +++ b/drivers/gpu/drm/i915/i915_gpu_error.c
> @@ -1643,9 +1643,16 @@ 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[9];
> +		if (ce)
> +			scnprintf(guc_id, sizeof(guc_id), "[0x%04X]", ce->guc_id.id);
> +		else
> +			scnprintf(guc_id, sizeof(guc_id), " ");
> +
> +		drm_info(&engine->gt->i915->drm, "Got hung context on %s with active request %lld:%lld%s not 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

      parent reply	other threads:[~2024-11-28 12:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-25 15:27 [PATCH v3] drm/i915: Fixed NULL pointer dereference in capture_engine Eugene Kobyak
2024-11-25 19:31 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Fixed NULL pointer dereference in capture_engine (rev3) Patchwork
2024-11-25 19:49 ` ✓ i915.CI.BAT: success " Patchwork
2024-11-25 22:33 ` ✗ i915.CI.Full: failure " Patchwork
2024-11-28 11:00 ` [PATCH v3] drm/i915: Fixed NULL pointer dereference in capture_engine Andi Shyti
2024-11-28 12:57 ` Jani Nikula [this message]

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=874j3r8qid.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox