Hi Cyrill, Programmers don't (and the manual-page says they shouldn't even try) call "sigreturn" directly.
If an interrupt happens, by bad luck, to occur while the process is running vdso code, then eventually, once signal-processing is complete, "sigreturn" (issued by glibc) will take the process back to where it was before the interrupt happend, inside the vdso page. Best Regards, Amnon. > On Mon, Nov 26, 2012 at 11:55:01PM +1100, Amnon Shiloh wrote: > > > > You could of course keep that old code and modify only the very > > first instruction of each routine into a jump instruction, but then > > the code to which the process returns may not be compatible with > > the new kernel and/or hardware configuration. > > For sure there will be some limitations but I fear we can't do > that much with it. I don't expect the regular program to use > sigreturn for jumping into vdso code, but I could be wrong. > > Cyrill > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
