From: Andi Shyti <andi.shyti@linux.intel.com>
To: Eugene Kobyak <eugene.kobyak@intel.com>
Cc: intel-gfx@lists.freedesktop.org, John.C.Harrison@intel.com,
andi.shyti@linux.intel.com, jani.nikula@linux.intel.com,
stable@vger.kernel.org
Subject: Re: [PATCH v6] drm/i915: Fix NULL pointer dereference in capture_engine
Date: Wed, 4 Dec 2024 15:43:09 +0100 [thread overview]
Message-ID: <Z1BqfTErA4t9L7Tc@ashyti-mobl2.lan> (raw)
In-Reply-To: <xmsgfynkhycw3cf56akp4he2ffg44vuratocsysaowbsnhutzi@augnqbm777at>
Hi Eugene,
On Tue, Dec 03, 2024 at 02:54:06PM +0000, Eugene Kobyak 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
> Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>
> Cc: John Harrison <John.C.Harrison@Intel.com>
> Cc: <stable@vger.kernel.org> # v6.3+
> Signed-off-by: Eugene Kobyak <eugene.kobyak@intel.com>
merged to drm-intel-next.
Thank you,
Andi
prev parent reply other threads:[~2024-12-04 14:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 14:54 [PATCH v6] drm/i915: Fix NULL pointer dereference in capture_engine Eugene Kobyak
2024-12-03 15:43 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Fix NULL pointer dereference in capture_engine (rev3) Patchwork
2024-12-03 15:58 ` ✗ i915.CI.BAT: failure " Patchwork
2024-12-03 17:06 ` [PATCH v6] drm/i915: Fix NULL pointer dereference in capture_engine Michal Wajdeczko
2024-12-04 10:32 ` Andi Shyti
2024-12-04 10:51 ` Jani Nikula
2024-12-04 11:04 ` Andi Shyti
2024-12-04 14:43 ` Andi Shyti [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=Z1BqfTErA4t9L7Tc@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 \
--cc=jani.nikula@linux.intel.com \
--cc=stable@vger.kernel.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.