| 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, 08 Feb 2007 11:12:49 -0500 From: Bill Davidsen <davidsen@....com> To: Geert Uytterhoeven <Geert.Uytterhoeven@...ycom.com> CC: Linux Frame Buffer Device Development <linux-fbdev-devel@...ts.sourceforge.net>, Linux Kernel Development <linux-kernel@...r.kernel.org> Subject: Re: 2.6.20: Modular fb and logo crash Geert Uytterhoeven wrote: > If you don't have any builtin frame buffer device driver and insmod a frame > buffer device driver, the logo code will still try to display the logo (which > is __initdata). This may cause a crash. > > Originally (2.1.x, is it that long ago I used a modular frame buffer device > driver?), this didn't happen because initmem_freed (which no longer exists) was > checked. BTW, there's still a comment in drivers/video/console/fbcon.c about > this. > > Anyone else who's seeing this? Anyone with an idea how to fix this? > Moving the logo code to userspace is not considered a solution ;-) I used to see this when loading from a booted system, but not when the modules were in initrd. Don't know if that offers you any help or not. Clearly you want the fb built-in so you see the penguins, anyway. ;-D -- Bill Davidsen <davidsen@....com> "We have more to fear from the bungling of the incompetent than from the machinations of the wicked." - from Slashdot - 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