intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Sergey Senozhatsky <senozhatsky@chromium.org>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
	Ville Syrjala <ville.syrjala@linux.intel.com>,
	Sergey Senozhatsky <senozhatsky@chromium.org>
Subject: Re: [PATCH 0/3] drm/i915/display: handle hdmi connector init failures
Date: Wed, 04 Dec 2024 17:08:44 +0200	[thread overview]
Message-ID: <877c8f32pv.fsf@intel.com> (raw)
In-Reply-To: <20241203123126.GE886051@google.com>

On Tue, 03 Dec 2024, Sergey Senozhatsky <senozhatsky@chromium.org> wrote:
> On (24/11/15 14:00), Sergey Senozhatsky wrote:
>> On (24/11/14 17:52), Jani Nikula wrote:
>> > This is an attempt to resolve [1].
>> > 
>> > [1] https://lore.kernel.org/r/20241031105145.2140590-1-senozhatsky@chromium.org
>> > 
>> > Jani Nikula (3):
>> >   drm/i915/hdmi: propagate errors from intel_hdmi_init_connector()
>> >   drm/i915/hdmi: add error handling in g4x_hdmi_init()
>> >   drm/i915/ddi: propagate errors from intel_ddi_init_hdmi_connector()
>> 
>> So these look reasonable and good to me, and I think landing them
>> makes a lot of sense.  For that part feel free to add:
>> 
>> Reported-and-tested-by: Sergey Senozhatsky <senozhatsky@chromium.org>
>> and FWIW
>> Reviewed-by: Sergey Senozhatsky <senozhatsky@chromium.org>
>> 
>> 
>> 
>> Now, regarding the issue in question - we are getting there, but not
>> quite there yet.
>> 
>> I'm still seeing multiple NULL-ptr derefs, namely on
>> 
>>  DDI A/PHY A
>>  DDI TC1/PHY TC1
>>  DDI TC2/PHY TC2
>>  DDI TC3/PHY TC3
>>  DDI TC4/PHY TC4
>> 
>> The thing is, all of them are DP connectors, we only ever call
>> intel_ddi_init_dp_connector() on them, so dig_port->hdmi
>> is not init-ed, wheres intel_hdmi_encoder_shutdown() doesn't
>> distinguish and treats everyone as HDMI connector, dereferencing
>> ->hdmi.
>> 
>> With the small addition I don't see null-ptr derefs anymore:
>
> Gentle ping on this.

v2 with two additional patches at [1].

BR,
Jani.

[1] https://lore.kernel.org/r/cover.1733324735.git.jani.nikula@intel.com

-- 
Jani Nikula, Intel

      reply	other threads:[~2024-12-04 15:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-14 15:52 [PATCH 0/3] drm/i915/display: handle hdmi connector init failures Jani Nikula
2024-11-14 15:52 ` [PATCH 1/3] drm/i915/hdmi: propagate errors from intel_hdmi_init_connector() Jani Nikula
2024-11-14 15:52 ` [PATCH 2/3] drm/i915/hdmi: add error handling in g4x_hdmi_init() Jani Nikula
2024-11-14 15:52 ` [PATCH 3/3] drm/i915/ddi: propagate errors from intel_ddi_init_hdmi_connector() Jani Nikula
2024-11-14 17:39 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915/display: handle hdmi connector init failures Patchwork
2024-11-14 17:39 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-11-14 17:40 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-11-15  5:00 ` [PATCH 0/3] " Sergey Senozhatsky
2024-12-03 12:31   ` Sergey Senozhatsky
2024-12-04 15:08     ` 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=877c8f32pv.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=senozhatsky@chromium.org \
    --cc=ville.syrjala@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;
as well as URLs for NNTP newsgroup(s).