[lkml]   [2008]   [Aug]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [RFC] [Patch 1/1] [Self Ptrace] System call notification with self_ptrace
    On 08/27, Pierre Morel wrote:
    > Oleg Nesterov wrote:
    > >On s390 the patch changes handle_signal(), this is not clear to me too.
    > >
    > The patch clears the trace flags before delivering the signal so
    > that the signal handler can use system call without bouncing again.

    Yes I see. But the signal handler for SIGSYS can fisrt do
    sys_ptrace(PTRACE_SELF_OFF) (which is filtered out), and then use any
    other syscall.

    With this patch PT_SELF is cleared on any signal. This doesn't look
    right. Let's suppose that another signal comes in parallel with SIGSYS.
    It is very possible that the handler for that another signal will be
    called first, this handler can do some syscall which will be "missed".

    > >Isn't it possible to implement this behaviour in the user space? If the
    > >task needs the PT_SELF behaviour, it can fork another process which will
    > >do PTRACE_ATTACH and then send the notifications to the task. We can use
    > >signals or something else.
    > >
    > In this case we would go back to standard ptrace behaviour.
    > The goal of the patch is to avoid the overhead of task switching
    > and IPC when instrumenting the process.

    Ah, I forgot to read the changelog, sorry.


     \ /
      Last update: 2008-08-27 18:23    [W:0.022 / U:6.436 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site