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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sun, 14 Oct 2007 09:15:35 +0200
From:	Manfred Spraul <>
To:	Yinghai Lu <>
CC:	Jeff Garzik <>,
	Ayaz Abdulla <>,
	nedev <>,
	Linux Kernel Mailing List <>,
	David Miller <>,
	Andrew Morton <>
Subject: Re: MSI interrupts and disable_irq

Yinghai Lu wrote:
> On 10/13/07, Manfred Spraul <> 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.


View attachment "patch-forcedeth-msi" of type "text/plain" (3044 bytes)

Powered by blists - more mailing lists