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: Fri, 23 Aug 2013 09:30:52 +0200 From: Ingo Molnar <mingo@...nel.org> To: Liu Ping Fan <kernelfans@...il.com> Cc: x86@...nel.org, linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>, "H. Peter Anvin" <hpa@...or.com>, Kevin Hao <haokexin@...il.com> Subject: Re: [PATCH] x86: ioapic needs check attr when programmed more than once * Liu Ping Fan <kernelfans@...il.com> wrote: > When programming ioapic pinX more than once, current code > does not check whether the later attr (trigger&polarity) is the > same as the former or not. This causes a broken semantic. > > Fix it by reporting -EBUSY, when attr is different. Was this observed in real life somehow, and if yes, what is the before/after behavior? Thanks, Ingo -- 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