Received: by 2002:a6b:500f:0:0:0:0:0 with SMTP id e15csp1845315iob; Fri, 29 Apr 2022 14:21:45 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwT3oQJoshy68iOjAfLFRMXXqWHEZUtF3KSDI1CA196ziw9Ks+QrNQ6G89WIZq/vGCXq+/0 X-Received: by 2002:a17:90a:a090:b0:1cb:a443:f19c with SMTP id r16-20020a17090aa09000b001cba443f19cmr1054883pjp.135.1651267304960; Fri, 29 Apr 2022 14:21:44 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1651267304; cv=none; d=google.com; s=arc-20160816; b=Lc+O3M47LdGqTW0mRFvvZWemRhjDUjugbi27BGIHow7RswSUMRr7e2DyjnnXdxj0F3 bJJAikw3UFrgKnUG+wL+ALa30e1IZAH4qIGH8edTr92qEVsNUCqXbjodom+Q3/LUaXG0 DSWcuXZVAHWe6P2EESP+GEKTrD8QZDM1ElCwAc4mcYRFqtzYT3B8O2OgqehK5lGMOX5k hYzv5nTPWW8ONir+9Bo6s8SKKWPY0eDRN1YAGtC4XYJQp74YPHdMU+qUhTPnjYucv9AP gmT9T4Xsrhuqy8mpb0OhI4Licpk/o0qAYTRx26tJaX1oKw/y8F9QQZH+0WrAWGc4UElz I3dQ== 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=MckBjl6pEvKZdqgy2wFZthz2dfKSJ3UYla219JW17Jw=; b=vD6nHa2WzxA9ucDGp8SQ2p2WVjqERKarXE0YkrJW/l1QlIkxUdQJB5+vH7gu4XtNgv l+4dffXpVyzuJR+v3jSKXuN7Jl71SGVRyOYXkAcXijEiKc/KHOJJyUj5lBa2T1zYYI8b DlSYFV31XDYZl4iDDs4u1sIKNS+XSJ04ZjevCJCZqwFlltqBiXd0SWlyYx7Gl72YZQ8j Gn4fz8E1eBipznp+YsiNrSP5s9CpPD+5mlDihom3zeye0q8kz4mqdD9zFHzTNyLnlDJH C4Yxf6Klpcfyg4iftlLo17smE6L1ayuN8mRoYiDeg7tN/I/smDQsMMoEa9gK1MVloVGK cA+w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=iyVvcK+P; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 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 out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id 192-20020a6301c9000000b003ab1f0ad455si8221241pgb.524.2022.04.29.14.21.28; Fri, 29 Apr 2022 14:21:44 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=iyVvcK+P; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 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 S1348674AbiD1PBY (ORCPT + 99 others); Thu, 28 Apr 2022 11:01:24 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53394 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S243847AbiD1PBW (ORCPT ); Thu, 28 Apr 2022 11:01:22 -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 D702A5DA29 for ; Thu, 28 Apr 2022 07:58:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1651157887; 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=MckBjl6pEvKZdqgy2wFZthz2dfKSJ3UYla219JW17Jw=; b=iyVvcK+P+xYwYTLIHDDwkv7sB/bFOp/uhpUG7TdTAoG2DexPmSdKbvKPL8dpKBSAx3/XyA vsAJTUKHKmOM7CXfw3T5XrLz4v4oCB3pLp0OQLG6oNiUbwN4/Udsso6WTPPgvkHQybN3jF CNNvYvPb/6hNBdxHWWzUQshhplOsocc= Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-157-LcUp97UwMqOoyRBIonnmcQ-1; Thu, 28 Apr 2022 10:57:58 -0400 X-MC-Unique: LcUp97UwMqOoyRBIonnmcQ-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.rdu2.redhat.com [10.11.54.1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 8E7103811F24; Thu, 28 Apr 2022 14:57:57 +0000 (UTC) Received: from dhcp-27-174.brq.redhat.com (unknown [10.40.192.151]) by smtp.corp.redhat.com (Postfix) with SMTP id A59CD407E1C0; Thu, 28 Apr 2022 14:57:52 +0000 (UTC) Received: by dhcp-27-174.brq.redhat.com (nbSMTP-1.00) for uid 1000 oleg@redhat.com; Thu, 28 Apr 2022 16:57:56 +0200 (CEST) Date: Thu, 28 Apr 2022 16:57:50 +0200 From: Oleg Nesterov To: Peter Zijlstra Cc: "Eric W. Biederman" , 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, 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 7/9] ptrace: Simplify the wait_task_inactive call in ptrace_check_attach Message-ID: <20220428145750.GA15485@redhat.com> References: <878rrrh32q.fsf_-_@email.froward.int.ebiederm.org> <20220426225211.308418-7-ebiederm@xmission.com> <20220427151455.GE17421@redhat.com> <20220428111911.GA3804@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.84 on 10.11.54.1 X-Spam-Status: No, score=-3.4 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_LOW, SPF_HELO_NONE,SPF_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/28, Peter Zijlstra wrote: > > On Thu, Apr 28, 2022 at 01:19:11PM +0200, Oleg Nesterov wrote: > > > That is also the reason I couldn't do wait_task_inactive(task, 0) > > > > Ah, I din't notice this patch uses wait_task_inactive(child, 0), > > I think it should do wait_task_inactive(child, __TASK_TRACED). > > Shouldn't we then switch wait_task_inactive() so have & matching instead > of the current ==. Sorry, I don't understand the context... As long as ptrace_freeze_traced() sets __state == __TASK_TRACED (as it currently does) wait_task_inactive(__TASK_TRACED) is what we need ? After we change it to use JOBCTL_DELAY_WAKEKILL and not abuse __state, ptrace_attach() should use wait_task_inactive(TASK_TRACED), but this depends on what exactly we are going to do... Oleg.