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: Tue, 29 May 2007 18:39:31 -0400 From: Jeff Garzik <jgarzik@...ox.com> To: Gary Zambrano <zambrano@...adcom.com> CC: Michael Buesch <mb@...sch.de>, Maximilian Engelhardt <maxi@...monizer.de>, linux-kernel <linux-kernel@...r.kernel.org>, linux-wireless <linux-wireless@...r.kernel.org>, Stephen Hemminger <shemminger@...ux-foundation.org>, Arnaldo Carvalho de Melo <acme@...stprotocols.net>, netdev@...r.kernel.org, Andrew Morton <akpm@...ux-foundation.org> Subject: Re: b44: regression in 2.6.22 (resend) Gary Zambrano wrote: > The b44 interrupt status reg returns a value of 0 if no interrupts are > pending. The b44 uses a mask to determine which bits (events) can > generate device interrupts on the system. If the masked interrupt status > register bits are not asserted, then the b44 will return to the system > with handled = 0. > So, I think the way the b44 interrupt code is written should be ok and > not a bug. This is normal. We check for 0xffffffff because that is often how a fault is indicated, when the memory location is read during or immediately after hotplug (or if the PCI bus is truly faulty). So for most hardware, you see tmp = read(irq status) if (!tmp) return irq-none /* no irq events raised */ if (tmp == 0xffffffff) return irq-none /* hot unplug or h/w fault */ and the method that determines no interrupt handling is needed. Regards, Jeff - 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