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: Wed, 24 Sep 2008 16:00:54 -0700 From: Greg KH <gregkh@...e.de> To: Linus Torvalds <torvalds@...ux-foundation.org>, Andrew Morton <akpm@...ux-foundation.org> Cc: linux-kernel@...r.kernel.org, Andreas Gruenbacher <agruen@...e.de>, Jeff Mahoney <jeffm@...e.de> Subject: [patch 00/04] RFC: Staging tree (drivers/staging) As we all discussed at the Kernel Summit this past week, I said I would create a drivers/staging directory and start throwing lots of drivers that are not of "mergable" status into it. For those not at the kernel summit, lwn.net has a summary of this session at: http://www.lwn.net/Articles/298570/ So, here's 4 patches for review/comments that show how this could be done. The first 2 patches create a TAINT_CRAP flag and set it for anything that comes from the drivers/staging/ directory. When a driver from this directory is loaded into the kernel, the user is warned, and any oops message that happens also properly shows the "bad" modules. The 3rd patch creates the drivers/staging/ directory and Kconfig entries and adds it to the build system. The 4th patch is an example of a driver that would go into this directory, along with a driver_name.README file detailing what needs to be done to this driver for cleanup/fixing, and who to contact about it. It's also in such bad shape it doesn't even build against the kernel kernel :) (I'll fix that up before submitting, all drivers should at least build properly...) So, does this all look good to everyone? Any questions/issues? Oh, I guess I should add a MAINTAINER entry for this section of the kernel, so to paraphrase Linus, I now get to be known as the "Maintainer of Crap". thanks, greg k-h -- 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