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
| ||
|
Date: Mon, 16 Jun 2014 14:00:33 +0900 From: Jongsung Kim <neidhard.kim@....com> To: Sören Brinkmann <soren.brinkmann@...inx.com> CC: netdev@...r.kernel.org, linux-kernel@...r.kernel.org, Nicolas Ferre <nicolas.ferre@...el.com>, "David S. Miller" <davem@...emloft.net>, Hayun Hwang <hwang.hayun@....com>, Youngkyu Choi <youngkyu7.choi@....com> Subject: Re: [PATCH] net/cadence/macb: clear interrupts simply and correctly On 06/13/2014 12:44 AM, Sören Brinkmann wrote: > Hi Jongsung, Hi Sören, > Does this interrupt need to be enabled? There is nothing checking > that bit and handling this IRQ in the handler, AFAICT. And you solve > this by simply clearing the bit. So, I wonder whether not enabling this > IRQ in the first place would solve things too. The driver actually checks the bit, but does not clear it. Disabling the "Rx used bit read" interrupt you said may be a solution. However, I think it is the better way to clear the exceptional HW-state rather than just to mask it. > This is now clearing all IRQ flags which is probably not what we want > here. This is handling RX only. We still want the non-RX interrupts to go to > the actual interrupt service routing. The ISR(Interrupt Status Register) is read only in the interrupt service routine, macb_interrupt. But is partially cleared here and there. Further handler-functions decide jobs to be done by reading/checking other status registers. (e.g., TSR, RSR) So, clearing the ISR after reading looks not a bad idea. Jongsung -- 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/
Powered by blists - more mailing lists