Re: [RFC] TIF_NOTIFY_RESUME, arch/*/*/*signal*.c and all such
From: Al Viro <viro@ZenIV.linux.org.uk>
Date: 2012-05-02 17:24:57
Also in:
lkml
Possibly related (same subject, not in this thread)
- 2012-05-02 · Re: [RFC] TIF_NOTIFY_RESUME, arch/*/*/*signal*.c and all such · Al Viro <viro@ZenIV.linux.org.uk>
- 2012-05-02 · Re: [RFC] TIF_NOTIFY_RESUME, arch/*/*/*signal*.c and all such · Matt Fleming <hidden>
- 2012-04-30 · Re: [RFC] TIF_NOTIFY_RESUME, arch/*/*/*signal*.c and all such · Greg Ungerer <hidden>
- 2012-04-29 · Re: [RFC] TIF_NOTIFY_RESUME, arch/*/*/*signal*.c and all such · Al Viro <viro@ZenIV.linux.org.uk>
- 2012-04-29 · Re: [RFC] TIF_NOTIFY_RESUME, arch/*/*/*signal*.c and all such · Oleg Nesterov <oleg@redhat.com>
On Tue, May 01, 2012 at 06:52:26AM +0100, Al Viro wrote:
IOW, here's what I'd suggest doing: * add that regs->orig_p0 = -1; to handle_restart() * add jump .Lresume_userspace_1 after the call of do_notify_resume() * instead of RESTORE_CONTEXT/rti in ret_from_fork and kernel_execve() have them jump to .Lresume_userspace.
arrrgh... The last one is unfortunately not so simple - you have that in the guts of _system_call, which is called via pseudo_long_call, so it would ought to be a call into the middle of _system_call, followed by that RESTORE_CONTEXT/rti...