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
Subject: Re: [PATCH v5] drm/i915: Fix NULL pointer dereference in capture_engine
Date: Tue, 3 Dec 2024 14:14:47 +0100 [thread overview]
Message-ID: <Z08ER6VLWmVOvfU5@ashyti-mobl2.lan> (raw)
In-Reply-To: <4yfdzisxkb3j3tig2astee5zd46ppt2jwhqffkhes2dwm3g5nb@snadyfwzl7g4>
Hi Eugene,
> Cc: <stable@vger.kernel.org> # v6.3+
Next time cc also the stable kernel mailing list for real,
please.
> + 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);
this is very ugly: %lld:%lld%snot I understand you leave a space
from the seqno and "not", but the form is unreadable. Could it be
better:
if (ce)
drm_info(.... ->guc_id);
else
drm_info(...); <-- same thing without the guc_id
It looks like for making it easier we are making it harder.
If you decide to go this way, perhaps you can add a comment
saying that ce might be NULL, but if it's not you want to keep
the guc_id information.
Next time cc also the stable kernel mailing list, please.
Thanks,
Andi
next prev parent reply other threads:[~2024-12-03 13:14 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
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 ` Andi Shyti [this message]
2024-12-03 14:40 ` ✓ i915.CI.Full: " 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=Z08ER6VLWmVOvfU5@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 \
/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