linux-kernel - Re: [PATCH 5.10 635/717] drm/amd/display: Honor the offset for plane 0.

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: <X+xHWBzD/L9Z7w97@kroah.com>
Date:   Wed, 30 Dec 2020 10:24:40 +0100
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Bas Nieuwenhuizen <bas@...nieuwenhuizen.nl>
Cc:     LKML <linux-kernel@...r.kernel.org>, stable@...r.kernel.org,
        Alex Deucher <alexander.deucher@....com>,
        Nicholas Kazlauskas <nicholas.kazlauskas@....com>
Subject: Re: [PATCH 5.10 635/717] drm/amd/display: Honor the offset for plane
 0.

On Tue, Dec 29, 2020 at 08:42:50PM +0100, Bas Nieuwenhuizen wrote:
> Hi Greg,
> 
> Someone bisected a non-booting computer with 5.10.4-rc1 to this
> commit. Would it be possible to back out of backporting this commit
> (was backported to 5.4 and 5.10)? I suspect we may need
> 53f4cb8b5580a20d01449a7d8e1cbfdaed9ff6b6 to be picked too to avoid
> regressing, but I'm not sure about process (e.g. timeline to confirm
> things) here and a not booting computer is really bad.

Thanks for the report, now dropped from both queues.  If this needs to
be added, after testing, please let stable@...r.kernel.org know and we
will be glad to add it back.

thanks,

greg k-h