vfork and clone do not work at all with sysenter due to user stack issues.
We should document that (it's already de-facto documented in glibc, but it
should be explicitly documented somewhere).
Btw, the vfork/clone problems aren't sysenter-specific per se: they are
really a generic problem with any non-inlined system call mechanism. In
particular, vfork() really cannot afford to have a stack frame.
> 2. A ptracer could use %ecx or %edx to pass information to signal
> handlers and this would not work with the current [rt_]sigsuspend.
Yes. Although I don't see why it should matter, really.
Linus
-
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/