Re: [PATCH 1/1] ptrace: do_notify_parent_cldstop: fix the wrong->nsproxy usage

[Roland McGrath]

> No, task_pid_vnr(current) in ptrace_notify() is not right. If the tracer
> does PTRACE_GETSIGINFO it gets the wrong .si_pid.

I don't follow.  PTRACE_GETSIGINFO gets the tracee's siginfo_t data--modulo
32/64 conversions it's the data structure the tracee process sees on its
stack when running a handler.  It's not like a signal sent into the
tracer's queue (like SIGCHLD in do_notify_*), where the kernel doing
translation to the tracer's context makes sense.  It's more like some
memory you read from the tracee.


Thanks,
Roland
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/