linux-kernel - Re: amdgpu_dm_connector_mode

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <a2dbbf4e79c42b99d0772db5712f52a430864240.camel@irl.hu>
Date: Thu, 24 Apr 2025 11:06:34 +0200
From: Gergo Koteles <soyer@....hu>
To:
  Marek Marczykowski-Górecki <marmarek@...isiblethingslab.com>
Cc: Dmitry Baryshkov <dbaryshkov@...il.com>,
  Dmitry Baryshkov <lumag@...nel.org>, regressions@...ts.linux.dev,
  dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org,
  amd-gfx@...ts.freedesktop.org, Hans de Goede <hdegoede@...hat.com>,
  Alex Deucher <alexander.deucher@....com>,
  Mario Limonciello <mario.limonciello@....com>,
  Alex Hung <alex.hung@....com>,
  Harry Wentland <harry.wentland@....com>
Subject: Re: amdgpu_dm_connector_mode_valid regression

Hi Marek,

On Thu, 2025-04-24 at 10:48 +0200, Marek Marczykowski-Górecki wrote:
> On Fri, Apr 11, 2025 at 12:01:28PM +0200, Marek Marczykowski-Górecki wrote:
> > 
> > Hi,
> > 
> > On Wed, Apr 02, 2025 at 04:35:05PM +0200, Gergo Koteles wrote:
> > > Hi Dmitry,
> > > 
> > > But the code would start to become quite untraceable.
> > > duplicate mode in amdgpu_dm_connector_mode_valid()
> > > call drm_mode_set_crtcinfo() in amdgpu_dm_connector_mode_valid()
> > > duplicate mode in create_stream_for_sink()
> > > overwrite ctrc in decide_crtc_timing_for_drm_display_mode()
> > > if crtc_clock == 0 call drm_mode_set_crtcinfo() again in
> > > create_stream_for_sink() 
> > 
> > FWIW I'm affected by the same issue (on HP ProBook 445 G7, with AMD
> > Ryzen 5 4500U). And the patch quoted below fixes it for me too.
> 
> I've re-tested it with 6.15-rc3 and the issue is still there. Is there
> something I can do to help fixing it before final 6.15 is out?
> 

This patch has been accepted into the the amd drm-fixes-6.15 branch, so
hopefully it will be fixed in 6.15-rc4.

https://lore.kernel.org/dri-devel/24439c13a014e1cd200785db6f3dcf08f4773eb3.1743612701.git.soyer@irl.hu/
https://gitlab.freedesktop.org/agd5f/linux/-/commits/drm-fixes-6.15

Gergo