linux-kernel - Framebuffer drivers that break the boot on systemswithout the hardware

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-next>] [day] [month] [year] [list]

Message-ID: <489DFACC.6030009@keyaccess.nl>
Date:	Sat, 09 Aug 2008 22:15:08 +0200
From:	Rene Herman <rene.herman@...access.nl>
To:	Antonino Daplas <adaplas@...il.com>
CC:	Ingo Molnar <mingo@...e.hu>, Andrew Morton <akpm@...l.org>,
	linux-fbdev-devel@...ts.sourceforge.net,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Framebuffer drivers that break the boot on systemswithout the hardware

Hi Antonino.

At:

http://lkml.org/lkml/2008/8/1/96

Ingo Molnar posted a list of drivers he found to break the boot during 
testing of randconfig kernels and among them are a number of FB drivers:

   FB_CIRRUS
   FB_ASILIANT
   FB_VGA16
   FB_VESA
   FB_RADEON
   FB_CYBLA
   (and FB_VIRTUAL)

Looking at some of them there wouldn't seem to be too many very sensible 
options to avoid this at the individual driver level. Would you perhaps 
have an idea how to avoid the issue generically for these?

More of the drivers in that list will  be considered fine as is but I 
was fixing some of the old legacy ISA ones as ofcourse any driver not 
needing special avoidance treatment is one less to have to deal with.

The randconfig testing IS useful in finding bugs, so...

Rene.

--
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/