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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87h5s34d36.fsf@jogness.linutronix.de>
Date: Fri, 30 Jan 2026 11:25:41 +0106
From: John Ogness <john.ogness@...utronix.de>
To:  Lyude Paul <lyude@...hat.com>, Danilo Krummrich <dakr@...nel.org>
Cc: Haneen Mohammed <hamohammed.sa@...il.com>,
    Sean Paul <seanpaul@...omium.org>, Simona Vetter <simona@...ll.ch>,
    dri-devel@...ts.freedesktop.org, nouveau@...ts.freedesktop.org,
    linux-kernel@...r.kernel.org
Subject: Re: nouveau regression with 6.19.0-rc7

On 2026-01-30, John Ogness <john.ogness@...utronix.de> wrote:
> On my workstation I have been using 6.19.0-rc4 with no problems. This
> morning I switched to 6.19.0-rc7 and now my graphics explodes when the
> nouveau module is loaded.

Reverting commit 604826acb3f5 ("drm/nouveau/disp: Set
drm_mode_config_funcs.atomic_(check|commit)") allows the nouveau driver
to load and work again.

Even though nouveau "technically supports atomic modesetting", it seems
more callbacks need to be implemented than just atomic_(check|commit).

Should I submit a patch with the revert? Or is there a quick fix to
allow drm_drv_uses_atomic_modeset() to return true and properly support
atomic modesetting?

John Ogness

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ