| 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: <Pine.LNX.4.64.0808201842350.18947@twin.jikos.cz> Date: Wed, 20 Aug 2008 18:46:05 +0200 (CEST) From: Jiri Kosina <jkosina@...e.cz> To: Linus Torvalds <torvalds@...ux-foundation.org> cc: Marcel Holtmann <marcel@...tmann.org>, "John W. Linville" <linville@...driver.com>, David Miller <davem@...emloft.net>, Andrew Morton <akpm@...ux-foundation.org>, netdev@...r.kernel.org, Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: [GIT]: Networking On Wed, 20 Aug 2008, Linus Torvalds wrote: > - but as a special case, we relax that for totally new drivers (and that > includes things like just adding a new PCI or USB ID's to old drivers), > because (a) it can't really regress It in fact depends on your definition of regression really :) If we merge a buggy driver that hangs the user's machine when loaded, well ... before the driver has been merged, the machine had been booting well, just some hardware was not functioning at all. After this late driver merge, the driver gets autoloaded upon boot and crashes the machine. Users will probably see this as a regression. This doesn't mean that I am against merging new drivers as aggressively as possible, I just wanted to point out that it might bring actual regressions to users. -- Jiri Kosina SUSE Labs -- 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