(restoring cc list) Andi Kleen wrote:
One of the other problems: NMIs and MCEs have the same problem with SYSCALL
This one however looks unsolvable. Userspace can point %rsp into arbitrary memory, issue a syscall, and hope for an nmi. Since we're in cpl 0 and are not using IST, the processor will not switch stacks, and the nmi stack frame will corrupt any memory the user chooses to point to.
Even without a malicious user, %rsp could legitimately point at unmapped memory.
I don't see how syscall could work on i386, and indeed:
vdso32.so-$(VDSO32-y) += int80 vdso32.so-$(CONFIG_COMPAT) += syscall vdso32.so-$(VDSO32-y) += sysenter
It's disabled. Is that the reason? -- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
