| 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
| ||
|
Message-ID: <20080701083036.32d20d1c@infradead.org> Date: Tue, 1 Jul 2008 08:30:36 -0700 From: Arjan van de Ven <arjan@...radead.org> To: Agner Fog <agner@...er.org> Cc: "H. Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org Subject: Re: ABI change for device drivers using future AVX instruction set On Sat, 28 Jun 2008 10:05:46 +0200 Agner Fog <agner@...er.org> wrote: > Arjan van de Ven wrote: > >the good news is that we review drivers before they get included > >and > we do catch such things. > > Are you saying that some group should have the monopoly of approving > device drivers? That is exectly the policy that Microsoft has been so > much criticized for. You can only control the drivers that are > included in your own Linux distribution. the linux model is that drivers (eventually) get included into the linux kernel source code. Everything we do process wise is centered around that concept. Nothing prevents you from going outside the process. But you need to realize that that is exactly that: outside the process. Meaning: you're partially on your own. -- If you want to reach me at my work email, use arjan@...ux.intel.com For development, discussion and tips for power savings, visit http://www.lesswatts.org -- 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