linux-kernel - Re: [PATCH] firmware/sysfb: Fix wrong stride when bits-per-pixel is calculated

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]

Date:   Wed, 12 Apr 2023 14:12:47 -0400
From:   "Pierre Asselin" <pa@...ix.com>
To:     "Javier Martinez Canillas" <javierm@...hat.com>
Cc:     "Pierre Asselin" <pa@...ix.com>,
        "Jocelyn Falempe" <jfalempe@...hat.com>,
        "Daniel Vetter" <daniel.vetter@...ll.ch>,
        linux-kernel@...r.kernel.org, dri-devel@...ts.freedesktop.org,
        "Hans de Goede" <hdegoede@...hat.com>,
        "Thomas Zimmermann" <tzimmermann@...e.de>,
        "Ard Biesheuvel" <ardb@...nel.org>
Subject: Re: [PATCH] firmware/sysfb: Fix wrong stride when bits-per-pixel is
 calculated

> Interesting. So you don't have the simplefb output that you had before ?

I do now, after a 'make clean' and "make bzImage'.

In between, I had tried CONFIG_SYSFB_SIMPLEFB=n .  That "works", by
falling back to vesafb in every case.  I restored the .config before
testing the patch, but there must have been leftover dregs in the
build tree.  1024x768x32 is garbled, others are good whether simplefb
or vesafb.

--PA