From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
Maxime Ripard <mripard@kernel.org>
Cc: Intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
Tvrtko Ursulin <tvrtko.ursulin@intel.com>,
Dan Carpenter <dan.carpenter@linaro.org>,
Jani Nikula <jani.nikula@intel.com>,
Luca Coelho <luciano.coelho@intel.com>,
Jani Nikula <jani.nikula@linux.intel.com>
Subject: Re: [PATCH] drm/i915: Fix possible null pointer dereference after drm_dbg_printer conversion
Date: Tue, 20 Feb 2024 09:16:43 +0000 [thread overview]
Message-ID: <f8455cd2-bed6-4026-bf6e-f6dfea2f86c5@linux.intel.com> (raw)
In-Reply-To: <ZdOz78jQu-GvJuDJ@intel.com>
On 19/02/2024 20:02, Rodrigo Vivi wrote:
> On Mon, Feb 19, 2024 at 01:14:23PM +0000, Tvrtko Ursulin wrote:
>> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>
>> Request can be NULL if no guilty request was identified so simply use
>> engine->i915 instead.
>>
>> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>> Fixes: d50892a9554c ("drm/i915: switch from drm_debug_printer() to device specific drm_dbg_printer()")
>> Reported-by: Dan Carpenter <dan.carpenter@linaro.org>
>> Cc: Jani Nikula <jani.nikula@intel.com>
>> Cc: Luca Coelho <luciano.coelho@intel.com>
>> Cc: Maxime Ripard <mripard@kernel.org>
>> Cc: Jani Nikula <jani.nikula@linux.intel.com>
>
> Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
Thanks Rodrigo!
Given how d50892a9554c landed via drm-misc-next, Maxime or Thomas -
could you take this via drm-misc-next-fixes or if there will be another
drm-misc-next pull request?
Regards,
Tvrtko
>
>> ---
>> drivers/gpu/drm/i915/gt/intel_engine_heartbeat.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/gt/intel_engine_heartbeat.c b/drivers/gpu/drm/i915/gt/intel_engine_heartbeat.c
>> index 5f8d86e25993..8d4bb95f8424 100644
>> --- a/drivers/gpu/drm/i915/gt/intel_engine_heartbeat.c
>> +++ b/drivers/gpu/drm/i915/gt/intel_engine_heartbeat.c
>> @@ -96,8 +96,8 @@ static void heartbeat_commit(struct i915_request *rq,
>> static void show_heartbeat(const struct i915_request *rq,
>> struct intel_engine_cs *engine)
>> {
>> - struct drm_printer p = drm_dbg_printer(&rq->i915->drm, DRM_UT_DRIVER,
>> - "heartbeat");
>> + struct drm_printer p =
>> + drm_dbg_printer(&engine->i915->drm, DRM_UT_DRIVER, "heartbeat");
>>
>> if (!rq) {
>> intel_engine_dump(engine, &p,
>> --
>> 2.40.1
>>
next prev parent reply other threads:[~2024-02-20 9:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 13:14 [PATCH] drm/i915: Fix possible null pointer dereference after drm_dbg_printer conversion Tvrtko Ursulin
2024-02-19 19:49 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2024-02-19 20:00 ` ✓ Fi.CI.BAT: success " Patchwork
2024-02-19 20:02 ` [PATCH] " Rodrigo Vivi
2024-02-20 9:16 ` Tvrtko Ursulin [this message]
2024-02-20 10:36 ` Maxime Ripard
2024-02-20 13:45 ` Tvrtko Ursulin
2024-02-20 3:54 ` ✓ Fi.CI.IGT: success for " Patchwork
2024-02-22 17:51 ` [PATCH] " Maxime Ripard
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=f8455cd2-bed6-4026-bf6e-f6dfea2f86c5@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=dan.carpenter@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=jani.nikula@linux.intel.com \
--cc=luciano.coelho@intel.com \
--cc=mripard@kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=tvrtko.ursulin@intel.com \
--cc=tzimmermann@suse.de \
/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