Re: [PATCH RESEND2] ptrace: make ptrace() fail if the tracee changed its pid unexpectedly

[Oleg Nesterov]

On 05/11, Oleg Nesterov wrote:
>
> On 05/11, Linus Torvalds wrote:
>
> > That said, why this:
> >
> > > +       rcu_read_lock();
> > > +       pid = task_pid_nr_ns(task, task_active_pid_ns(task->parent));
> > > +       rcu_read_unlock();
> >
> > I don't see why the RCU read lock would be needed? task_pid_nr_ns()
> > does any required locking itself, afaik.
> >
> > And even if it wasn't, this all happens with siglock held, can
> > anything actually change.
>
> ... and with tasklist_lock held.
>
> Hmm. Linus, I am shy to admit I can't answer immediately, I'll recheck
> tomorrow after sleep. But it seems you are right.

most probably to protect task->parent, not sure, this was 6 month ago...
but in this case we can use "current". I'll recheck.

> Thanks!

Oleg.