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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 02 Nov 2006 21:55:36 +0000 From: Alan Cox <alan@...rguk.ukuu.org.uk> To: Andrew Morton <akpm@...l.org> Cc: "Rafael J. Wysocki" <rjw@...k.pl>, Auke Kok <auke-jan.h.kok@...el.com>, Jesse Brandeburg <jesse.brandeburg@...el.com>, Adrian Bunk <bunk@...sta.de>, LKML <linux-kernel@...r.kernel.org>, Linus Torvalds <torvalds@...l.org>, Laurent Riffard <laurent.riffard@...e.fr>, Rajesh Shah <rajesh.shah@...el.com>, toralf.foerster@....de, Jeff Garzik <jeff@...zik.org>, Pavel Machek <pavel@....cz>, Greg KH <greg@...ah.com> Subject: Re: 2.6.19-rc4: known unfixed regressions Ar Iau, 2006-11-02 am 12:10 -0800, ysgrifennodd Andrew Morton: > Balls are being dropped. > > > http://bugzilla.kernel.org/show_bug.cgi?id=7082 > > So this was a good patch but because of a bug in ne2k-pci which nobody is > fixing we need to drop it? I believe the patch is fundamentally wrong. We don't *need* to drop the IO decode in this case. We don't want to drop it when the BIOS lacks the brains to put it back. We will also kill some machines doing it as they have devices we attach drivers to which are not just managing the function Linux knows about but also many other things. Take the CS5520 for example, generically disable the I/O on that because we have an IDE driver attached to it and you kill the box stone dead, as its also the video and a few other things behind the scenes. That is not atypical. IFF someone has a device that actually needs to disable I/O cycles, well they can do it themselves. Alan - 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