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: Sun, 14 Oct 2007 16:15:46 -0700 From: "Yinghai Lu" <yhlu.kernel@...il.com> To: benh@...nel.crashing.org Cc: "Manfred Spraul" <manfred@...orfullife.com>, "Jeff Garzik" <jgarzik@...ox.com>, "Ayaz Abdulla" <aabdulla@...dia.com>, nedev <netdev@...r.kernel.org>, "Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>, "David Miller" <davem@...emloft.net>, "Andrew Morton" <akpm@...ux-foundation.org> Subject: Re: MSI interrupts and disable_irq On 10/14/07, Benjamin Herrenschmidt <benh@...nel.crashing.org> wrote: > > On Sun, 2007-10-14 at 09:15 +0200, Manfred Spraul wrote: > > Yinghai Lu wrote: > > > On 10/13/07, Manfred Spraul <manfred@...orfullife.com> wrote: > > > > > >> Someone around with a MSI capable board? The forcedeth driver does > > >> dev->irq = pci_dev->irq > > >> in nv_probe(), especially before pci_enable_msi(). > > >> Does pci_enable_msi() change pci_dev->irq? Then we would disable the > > >> wrong interrupt.... > > >> > > > > > > the request_irq==>setup_irq will make dev->irq = pci_dev->irq. > > > > > > > > Where is that? > > Otherwise I would propose the attached patch. My board is not > > MSI-capable, thus I can't test it myself. > > Why not just copy pcidev->irq to dev->irq once ? it seems e1000 is using np->pci_dev->irq directly too. YH - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists