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
| ||
|
Date: Thu, 19 Dec 2013 13:31:37 +0100 From: Ingo Molnar <mingo@...nel.org> To: David Herrmann <dh.herrmann@...il.com> Cc: One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>, linux-kernel <linux-kernel@...r.kernel.org>, Takashi Iwai <tiwai@...e.de>, Stephen Warren <swarren@...dotorg.org>, "linux-fbdev@...r.kernel.org" <linux-fbdev@...r.kernel.org>, the arch/x86 maintainers <x86@...nel.org> Subject: Re: cirrusdrmfb broken with simplefb * David Herrmann <dh.herrmann@...il.com> wrote: > Hi > > On Thu, Dec 19, 2013 at 1:03 AM, One Thousand Gnomes > <gnomes@...rguk.ukuu.org.uk> wrote: > >> > That bug always existed, simplefb is just the first driver to hit it > >> > (vesafb/efifb didn't use resources). I'm aware of the issue but as a > >> > workaround you can simply disable CONFIG_X86_SYSFB. That restores > >> > the old behavior. > >> > >> This looks like a regression, so we'll either need a fix or we'll have > >> to mark CONFIG_X86_SYSFB as CONFIG_BROKEN. > > > > Kernel bugzilla has entries for simplefb breaking both vesafb and > > matrox mga. > > Thanks for the hints. I've read through all I could find and tried > to provide some help. > > I'm kind of confused, most of them enable CONFIG_X86_SYSFB (which is > 'n' by default) but don't read the help text. I did my best to tell > people that this option requires CONFIG_FB_SIMPLE, but if you don't > read the help-text you won't notice that. Don't know what to do > about that.. People generally don't read the help text - still the kernel should not break. So please the Kconfig angle (and the bootup logic, etc.) fool-proof, graphics failures are not fun to debug! Thanks, Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists