Received: by 2002:a05:6602:2086:0:0:0:0 with SMTP id a6csp4648225ioa; Wed, 27 Apr 2022 08:11:55 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwbU17xhPCcJBXtiEHOoNM1YyyU0NkVhS69HHdiWZat/GNcDB7LrQcW9ctt1n/n5bPMMgZ2 X-Received: by 2002:a05:6830:446:b0:605:5cbc:f670 with SMTP id d6-20020a056830044600b006055cbcf670mr10339720otc.29.1651072314890; Wed, 27 Apr 2022 08:11:54 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1651072314; cv=none; d=google.com; s=arc-20160816; b=FyVP0HdJJ/GxvxLHho1lMy8Pg20KnZXAGpyX7EAS3TGI7VYdjn8TGE+vEfgUainKq6 B6nxBuGM+TXSwRNBRRXmDJto2x+YSNcrvT1vOVL1x10yu59K+OESFhrnuAylshs9hnqh Yq3mbSLyDH57VyQiFIcn5haSHbvJpGb27rbHQj19g6aZMfzawAXOWtNlj4xR7LZxRzo4 u9LX6aUotgbTXqVS7hWECKXnNqkZsdMFJFNRmvYDBFvPfyYLSbcIAM8VlInPEGr7uemn GmzzUU6C94/FYK6n4v31ZOdB0puCoCn0M0cNZQfali2LoTodgEt2EC7nithuAkpT9vVL dx9Q== 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=G9DkRJaDUMwY7Wxq8Elonr7u7Py6sFY37e6s/qu71Og=; b=f0QiTcdf0MxvmZvfQ3PzFau5S1ERafU54rTXdWm7maEDPGPa1qE6psnBf/NTEsrVsf 9XhDIswtpNBLdqCTvhmEs4I4UbN7Rg2QdmvTk6loi4C4d2ozCiuLrucr6vMrizYEBQ9Q FQBZz2HZxztvOyu99SJffROlgE18C91wx75qI6G+MdYCEElcuodPWnHb86Ttc726iNkp KjWeu0dnkwuiZwUjXKhSHFxIWUpVaz3WzxO7UuAUluIgeVzQ9eCm0rttVJuidb4af5mX xHjxsxgxQji0ZmRba4N+E+3EN2UFrPrdGhC/XzGS66vTZAswXyzUzZcyXMsJyjKSsv+O uXJA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=U6jPjTHq; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 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 lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [23.128.96.19]) by mx.google.com with ESMTPS id d62-20020acab441000000b00322a71a7ef4si856463oif.3.2022.04.27.08.11.49 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 27 Apr 2022 08:11:54 -0700 (PDT) Received-SPF: softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=U6jPjTHq; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id EB35236E10; Wed, 27 Apr 2022 07:43:33 -0700 (PDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238443AbiD0Oqi (ORCPT + 99 others); Wed, 27 Apr 2022 10:46:38 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58288 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238429AbiD0Oq0 (ORCPT ); Wed, 27 Apr 2022 10:46:26 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 36A2E3669C for ; Wed, 27 Apr 2022 07:43:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1651070593; 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=G9DkRJaDUMwY7Wxq8Elonr7u7Py6sFY37e6s/qu71Og=; b=U6jPjTHqtOYnBdUDhggW/2RRQNwqgVs7uR/Hxao2tXmwsaEOiUPjsQSUuqyaLHIxUBrX/z 2qopU8u8pETruwle7t7EmgU8fVT1ZPoYpx37rC5kbFeLzD4IrPmq481bFbFdt/pvaiv81o Rgq5V0qMnOu0avx5UQ4M7YWBhB5FFo4= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-553-0sTi6ypeNaG65Sxn8qbA6A-1; Wed, 27 Apr 2022 10:43:07 -0400 X-MC-Unique: 0sTi6ypeNaG65Sxn8qbA6A-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.rdu2.redhat.com [10.11.54.2]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 7798D802803; Wed, 27 Apr 2022 14:43:06 +0000 (UTC) Received: from dhcp-27-174.brq.redhat.com (unknown [10.40.192.128]) by smtp.corp.redhat.com (Postfix) with SMTP id A174E40D282F; Wed, 27 Apr 2022 14:43:01 +0000 (UTC) Received: by dhcp-27-174.brq.redhat.com (nbSMTP-1.00) for uid 1000 oleg@redhat.com; Wed, 27 Apr 2022 16:43:06 +0200 (CEST) Date: Wed, 27 Apr 2022 16:43:00 +0200 From: Oleg Nesterov To: "Eric W. Biederman" Cc: linux-kernel@vger.kernel.org, rjw@rjwysocki.net, mingo@kernel.org, vincent.guittot@linaro.org, dietmar.eggemann@arm.com, rostedt@goodmis.org, mgorman@suse.de, bigeasy@linutronix.de, Will Deacon , tj@kernel.org, linux-pm@vger.kernel.org, Peter Zijlstra , Richard Weinberger , Anton Ivanov , Johannes Berg , linux-um@lists.infradead.org, Chris Zankel , Max Filippov , inux-xtensa@linux-xtensa.org, Kees Cook , Jann Horn Subject: Re: [PATCH 6/9] signal: Always call do_notify_parent_cldstop with siglock held Message-ID: <20220427144259.GB17421@redhat.com> References: <878rrrh32q.fsf_-_@email.froward.int.ebiederm.org> <20220426225211.308418-6-ebiederm@xmission.com> <20220427141018.GA17421@redhat.com> <874k2ea9q4.fsf@email.froward.int.ebiederm.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <874k2ea9q4.fsf@email.froward.int.ebiederm.org> User-Agent: Mutt/1.5.24 (2015-08-30) X-Scanned-By: MIMEDefang 2.84 on 10.11.54.2 X-Spam-Status: No, score=-2.5 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RDNS_NONE,SPF_HELO_NONE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 04/27, Eric W. Biederman wrote: > > The ptrace parental relationship definitely has the potential to be a > graph with cycles. Which as you point out is not fine. > > The result is very nice and I don't want to give it up. I suspect > something ptrace cycles are always a problem and can simply be > forbidden. OK, please consider another case. We have a parent P and its child C. C traces P. This is not that unusual, I don't think we can forbid this case. P reports an event and calls do_notify_parent_cldstop(). C receives SIGSTOP and calls do_notify_parent_cldstop() too. Oleg.