| 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: Fri, 25 Jan 2008 17:01:15 +0100 (CET) From: Jan Engelhardt <jengelh@...putergmbh.de> To: Jon Masters <jcm@...hat.com> cc: Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>, Andrew Morton <akpm@...ux-foundation.org>, Valdis.Kletnieks@...edu, "Frank Ch. Eigler" <fche@...hat.com>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Rusty Russell <rusty@...tcorp.com.au>, Christoph Hellwig <hch@...radead.org>, Linus Torvalds <torvalds@...ux-foundation.org> Subject: Re: [PATCH] Linux Kernel Markers Support for Proprierary Modules On Jan 25 2008 10:31, Jon Masters wrote: >On Fri, 2008-01-25 at 08:56 +0100, Jan Engelhardt wrote: > >> So what is needed is an Oops with an explaining message >> if (kernel_tainted) "blame that proprietary module first", >> and make sure the user sees that oops even if in X. > >The former is actually trivially doable with the module->taints bits. We >could have the equivalent of a neon flashing "blame this module" sign. > >I also agree, we should stop force loading. Incompatible struct module, >etc. are really bad things to have mapped into a running kernel. Forceloading should be reserved for developers who know when a symversion change is safe (which is rare in itself, but still). -- 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