Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Tue, 11 May 2021 20:06:28 +0200
From:   Oleg Nesterov <oleg@redhat.com>
To:     Linus Torvalds <torvalds@linux-foundation.org>
Cc:     Andrew Morton <akpm@linux-foundation.org>,
        "Eric W. Biederman" <ebiederm@xmission.com>,
        Eugene Syromiatnikov <esyr@redhat.com>,
        Jan Kratochvil <jan.kratochvil@redhat.com>,
        Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
        Michael Kerrisk <mtk.manpages@gmail.com>,
        Pedro Alves <palves@redhat.com>,
        Simon Marchi <simon.marchi@efficios.com>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RESEND2] ptrace: make ptrace() fail if the tracee changed
 its pid unexpectedly
Message-ID: <20210511180627.GB14488@redhat.com>
References: <20210511165626.GA13720@redhat.com>
 <CAHk-=whLqbTNc1T+rHCm-kxbVAuhK3hjo5fOgDVf5-z--x1mvQ@mail.gmail.com>
 <20210511175341.GA14488@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20210511175341.GA14488@redhat.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Precedence: bulk

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.