| 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: Tue, 8 Nov 2011 20:25:35 +0530 From: "Shilimkar, Santosh" <santosh.shilimkar@...com> To: Marc Zyngier <marc.zyngier@....com> Cc: linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de> Subject: Re: [PATCH] genirq: don't allow per cpu interrupts to be suspended On Tue, Nov 8, 2011 at 8:18 PM, Marc Zyngier <marc.zyngier@....com> wrote: > The power management functions related to interrupts do not know > (yet) about per-cpu interrupts and end up calling the wrong > low-level methods to enable/disable interrupts. > > This leads to all kind of interesting issues (action taken on one > CPU only, updating a refcount which is not used otherwise...). > > The workaround for the time being is simply to flag these interrupts > with IRQF_NO_SUSPEND. At least on ARM, these interrupts are actually > dealt with at the architecture level. > > Reported-by: Santosh Shilimkar <santosh.shilimkar@...com> > Cc: Thomas Gleixner <tglx@...utronix.de> > Signed-off-by: Marc Zyngier <marc.zyngier@....com> > --- Just to add, the suspend is broken on mainline for ARM machines which are using IRQCHIP_MASK_ON_SUSPEND. The $subject patch fixes that issue. Tested-by: Santosh Shilimkar <santosh.shilimkar@...com> Regards, Santosh -- 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