| 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, 26 Oct 2006 15:41:17 +0100 From: Al Viro <viro@....linux.org.uk> To: Alan Cox <alan@...rguk.ukuu.org.uk> Cc: Andrew Morton <akpm@...l.org>, proski@....org, linux-kernel@...r.kernel.org Subject: Re: incorrect taint of ndiswrapper On Thu, Oct 26, 2006 at 11:39:59AM +0100, Alan Cox wrote: > Ar Mer, 2006-10-25 am 20:59 -0700, ysgrifennodd Andrew Morton: > > May be so. But this patch was supposed to print a helpful taint message to > > draw our attention to the fact that ndis-wrapper was in use. The patch was > > not intended to cause gpl'ed modules to stop loading > > The stopping loading is purely because it now uses _GPLONLY symbols, > which is fine until the user wants to load a windows driver except for > the old CIPE driver. Some assumptions broke somewhere along the way and > the chain of events that was never forseen unfolded. Could we please decide WTF _GPLONLY *is* and at least remain consistent? Aside of "method of fighting binary-only modules", that is - this part is obvious. I'm not fond of ndiswrapper and stuff it uses, but AFAICS the list of symbols it uses doesn't look like poking in the guts of kernel. ISTR explanations along the lines of "well, it's for the stuff that shouldn't be used by out-of-tree code". Does anybody still subscribe to that or should that be considered a pure smokescreen? - 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