Messages in this thread | | | Date | Sat, 3 Mar 2007 02:11:03 +0300 | From | Oleg Nesterov <> | Subject | Re: + fully-honor-vdso_enabled.patch added to -mm tree |
| |
On 03/02, Chuck Ebbert wrote: > > John Reiser wrote: > > The value of ->sysenter_return is interpreted in user space by the > > sysexit instruction; nobody else cares what the value is. The kernel > > is not required to provide a good value when vdso_enabled is zero, > > because the kernel has not told the process that sysenter is valid > > (by setting AT_SYSINFO.) > > Doesn't matter because a malicious user can still execute sysenter. > We do have to deal with that somehow, so we have to put something > safe in there.
Yes, but a malicious user can't make any harm to the system, sysexit jumps to ->sysenter_return when user_mode() is true, right?
(I am asking because I don't know in details what sysexit does).
Oleg.
- 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/
| |