Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp3745221pxj; Tue, 11 May 2021 10:57:21 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzw1Pk+fplQ6+pmZZOygRdEVvI0SrA53/vrJRJ2GvytDtuGbEobQVuB1/EGpi0LsxeJK5lh X-Received: by 2002:a17:906:a294:: with SMTP id i20mr1920898ejz.86.1620755840918; Tue, 11 May 2021 10:57:20 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1620755840; cv=none; d=google.com; s=arc-20160816; b=bxrSTzuMIzHIvJHYw7brqvzwQvludvMO/OqeJGZErS7AzPWn6TE9NCHKLqbzJ8Q/YQ x/2cucxOAf3O7rpcI8HeVGOtB+CmEHoAKv3PtI/JqSy3z4rNGxOn54P1mGSRUSv9fmEF M2t0v5vkjignLsOA16yb2ZvEqvNaibx9SWuFnPGdt8fqnroRDeQMppDcSqiw/3k4aWKl C3CB1qgqxB4HdHyIma77Pp0dJ1ni2smodIt4PHcHSJAgmfjrLuadTP3ScRrvoCfNSYaU F1GvPKrEc1WSBnVGNWVtnJMm+ouQkclI0BCjbRFHCmS/U2p/giNQx8GgqafKFWFCZ+IV Zyiw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=TMmnYi2R2rpijnadia4P/sKG3RmewE+fpb6vPJAQNH4=; b=l4vpinpFzW1QMvO5h633VjtuCdbgmrD97P0Sc0m6JVoNZ9h7PHLxYzNGjr8axz+J38 ObQuJvLz4Yyu1bi5voMEuWKiTY7sYz6GraKG2QOrC+euX8ofQ+Y1Yb0BlNGHRWOdEqmP o4j24TGXQx6m/mFYC6kQC4QVz9mjQ54DIhjdA4+7fM3C/szMyXqfxA9whKtTKJ2pW9hM 5Gxm39DdeVq9AbcRagNzwMA9xKt8LIepoa+OL2LEy7I4XcMysUNlfuOsLkWOv0pDnVF+ eZx242XfonbdtlNgfDwHxDYytdUuNcTQeqrvRUuaRbh+Pci+ld6zn/VDT2nuCiBnEsgX J+/Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=ZiiAoLYF; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id l12si15715309edc.467.2021.05.11.10.56.56; Tue, 11 May 2021 10:57:20 -0700 (PDT) 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; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=ZiiAoLYF; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231512AbhEKRzF (ORCPT + 99 others); Tue, 11 May 2021 13:55:05 -0400 Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]:23027 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231439AbhEKRzD (ORCPT ); Tue, 11 May 2021 13:55:03 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1620755636; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=TMmnYi2R2rpijnadia4P/sKG3RmewE+fpb6vPJAQNH4=; b=ZiiAoLYF0/wwuWwZzzDeAk027Az9FnVUVoRP2WgEdjawXdF5rVJNXX1kiHlnMHq9GW/Rk+ EWCpr3FhnLwf0fRBY5JI26yvdjwWH5V/HHdSAFyZq0s/ofxUP0BSC3sOZIqNF3wi9e32aP 4fQKM+om6wfc0WzJZOMT2ZUf0yOebOo= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-165-0Ghno32cNDCf2rniGd5djw-1; Tue, 11 May 2021 13:53:55 -0400 X-MC-Unique: 0Ghno32cNDCf2rniGd5djw-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 55ED3106BB24; Tue, 11 May 2021 17:53:53 +0000 (UTC) Received: from dhcp-27-174.brq.redhat.com (unknown [10.40.192.124]) by smtp.corp.redhat.com (Postfix) with SMTP id C8EAF2B431; Tue, 11 May 2021 17:53:43 +0000 (UTC) Received: by dhcp-27-174.brq.redhat.com (nbSMTP-1.00) for uid 1000 oleg@redhat.com; Tue, 11 May 2021 19:53:52 +0200 (CEST) Date: Tue, 11 May 2021 19:53:42 +0200 From: Oleg Nesterov To: Linus Torvalds Cc: Andrew Morton , "Eric W. Biederman" , Eugene Syromiatnikov , Jan Kratochvil , Mathieu Desnoyers , Michael Kerrisk , Pedro Alves , Simon Marchi , Linux Kernel Mailing List Subject: Re: [PATCH RESEND2] ptrace: make ptrace() fail if the tracee changed its pid unexpectedly Message-ID: <20210511175341.GA14488@redhat.com> References: <20210511165626.GA13720@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 05/11, Linus Torvalds wrote: > > On Tue, May 11, 2021 at 9:56 AM Oleg Nesterov wrote: > > > > This patch makes ptrace() fail in this case until debugger does wait() > > and consumes PTHREAD_EVENT_EXEC which reports old_pid. > > I'm ok with the patch, just wondering which way it's supposed to come > to me. Should I just apply it directly? would be nice! > 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. Thanks! Oleg.