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, 20 Mar 2007 09:06:15 -0700 (PDT) From: Linus Torvalds <torvalds@...ux-foundation.org> To: "Eric W. Biederman" <ebiederm@...ssion.com> cc: Jeremy Fitzhardinge <jeremy@...p.org>, Zachary Amsden <zach@...are.com>, Rusty Russell <rusty@...tcorp.com.au>, Andi Kleen <ak@....de>, David Miller <davem@...emloft.net>, mingo@...e.hu, akpm@...ux-foundation.org, linux-kernel@...r.kernel.org, virtualization@...ts.osdl.org, xen-devel@...ts.xensource.com, chrisw@...s-sol.org, anthony@...emonkey.ws, netdev@...r.kernel.org Subject: Re: [patch 13/26] Xen-paravirt_ops: Consistently wrap paravirt ops callsites to make them patchable On Tue, 20 Mar 2007, Eric W. Biederman wrote: > > If that is the case. In the normal kernel what would > the "the oops, we got an interrupt code do?" > I assume it would leave interrupts disabled when it returns? > Like we currently do with the delayed disable of normal interrupts? Yeah, disable interrupts, and set a flag that the fake "sti" can test, and just return without doing anything. (You may or may not also need to do extra work to Ack the hardware interrupt etc, which may be irq-controller specific. Once the CPU has accepted the interrupt, you may not be able to just leave it dangling) But I was throwing that out as a long-term thing. I'm not claiming it's trivial, but it should be doable. Linus - 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