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
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 02 Nov 2006 21:55:36 +0000
From:	Alan Cox <>
To:	Andrew Morton <>
Cc:	"Rafael J. Wysocki" <>,
	Auke Kok <>,
	Jesse Brandeburg <>,
	Adrian Bunk <>,
	LKML <>,
	Linus Torvalds <>,
	Laurent Riffard <>,
	Rajesh Shah <>,,
	Jeff Garzik <>, Pavel Machek <>,
	Greg KH <>
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.
> >
> 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.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists