![]() | ||||||||||
Messages in this thread |
Ingo Molnar wrote: > and i'm 100% sure the more robust eflags saving will also avoid security > holes. The amount of security-relevant complexity that comes from all the > x86 features [and their combinations] is amazing. Userspace can skip the "popfl" with a well-timed signal. If the "sysexit" path leaves the kernel with an unsafe eflags, that will propagate into the signal handler. AFAICT, one of these is required: 1. eflags must be safe before leaving kernel space, or 2. setup_sigcontext() must clean it up (it already does clear TF). -- Jamie - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | |||||||||
| Last update: 2005-03-22 11:31 [W:1.744 / U:0.060 seconds] ©2003-2008 Jasper Spaans | ||||||||||