linux-kernel - Re: Disable INTx when enabling MSI

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0612071745270.20138@iabervon.org>
Date:	Thu, 7 Dec 2006 18:04:04 -0500 (EST)
From:	Daniel Barkalow <barkalow@...ervon.org>
To:	Greg KH <gregkh@...e.de>
cc:	Jeff Garzik <jeff@...zik.org>, Linus Torvalds <torvalds@...l.org>,
	linux-kernel@...r.kernel.org
Subject: Re: Disable INTx when enabling MSI

On Thu, 7 Dec 2006, Greg KH wrote:

> Care to take Jeff's proposed patch, verify that it works and forward it
> on to me?

I'll test it tomorrow. Testing disables my network, and making sure the 
problem exists without the patch kills my disk controller, so I need to 
sit at the computer for a while. I assume that I've got the only known 
device that demonstrates the need for this?

Off topic: would it be wise as a general rule to somehow shut down devices 
whose interrupts get disabled by the "nobody cared!" code? Or maybe call 
their interrupt handlers periodically to keep them alive?

	-Daniel
*This .sig left intentionally blank*
-
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/