linux-kernel - Re: [patch] PCI: disable MSI on more ATI NorthBridges

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <471DC9A7.3080105@garzik.org>
Date:	Tue, 23 Oct 2007 06:15:03 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Daniel Barkalow <barkalow@...ervon.org>
CC:	Linas Vepstas <linas@...tin.ibm.com>,
	Shane Huang <chunhao.huang@...mail.com>, davem@...emloft.net,
	gregkh@...e.de, htejun@...il.com, brice.goglin@...il.com,
	david.gaarenstroom@...il.com, linux-kernel@...r.kernel.org,
	linux-pci@...ey.karlin.mff.cuni.cz, shane.huang@....com,
	linux-ide@...r.kernel.org, Brice Goglin <brice@...i.com>
Subject: Re: [patch] PCI: disable MSI on more ATI NorthBridges

Daniel Barkalow wrote:
> I have a device that supports MSI and INTX-disable, and, with MSI on (and 
> delivering interrupts successfully) also sends legacy interrupts (on 
> the IRQ that is no longer associated with the device) unless INTX is 
> disabled. Without the intx_disable(), the kernel disables the IRQ 
> entirely and breaks a random other device in my system.


That sort of behavior is an example of why I wrote pci_intx() in the 
first place, and employed it by default throughout the ATA drivers 
(before it migrated into PCI core).

	Jeff


-
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/