Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Shyti <andi.shyti@linux.intel.com>
To: Eugene Kobyak <eugene.kobyak@intel.com>
Cc: intel-gfx@lists.freedesktop.org, andi.shyti@linux.intel.com,
	John.C.Harrison@intel.com
Subject: Re: [PATCH v2] drm/i915: Fixed NULL pointer dereference in capture_engine
Date: Wed, 20 Nov 2024 16:12:52 +0100	[thread overview]
Message-ID: <Zz38dANRGWYgvdCQ@ashyti-mobl2.lan> (raw)
In-Reply-To: <jpbxlab2hz4gozye45lcl635zc4nrfb7rsrvgk4jlfgww2yo6g@qriixepb57au>

Hi Eugene,

On Wed, Nov 20, 2024 at 03:03:29PM +0000, Eugene Kobyak wrote:
> When the intel_context structure contains NULL,
> it raises a NULL pointer dereference error in drm_info().
> 
> This patch aims to resolve issue:
> https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/12309
> 
> Signed-off-by: Eugene Kobyak <eugene.kobyak@intel.com>

Looks better, but you forgot:

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+

(Note the second line, Closes, this is how the gitlab issue
should be reported).

No worries, if John doesn't have anything agains, I can fix it.

But I was actually thinking here that the guc_id can be also
taken from engine->guc_id, I think it's the same.

Andi

  reply	other threads:[~2024-11-20 15:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-20 15:03 [PATCH v2] drm/i915: Fixed NULL pointer dereference in capture_engine Eugene Kobyak
2024-11-20 15:12 ` Andi Shyti [this message]
2024-11-20 15:55 ` ✓ Fi.CI.BAT: success for drm/i915: Fixed NULL pointer dereference in capture_engine (rev2) Patchwork
2024-11-21  9:24 ` ✗ i915.CI.Full: failure " Patchwork
2024-11-21 23:44 ` [PATCH v2] drm/i915: Fixed NULL pointer dereference in capture_engine John Harrison

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=Zz38dANRGWYgvdCQ@ashyti-mobl2.lan \
    --to=andi.shyti@linux.intel.com \
    --cc=John.C.Harrison@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