Received: by 2002:a05:6a10:5594:0:0:0:0 with SMTP id ee20csp599777pxb; Mon, 25 Apr 2022 17:49:03 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzFowQdOTJSEEd9zT9TSa9wZIRs3NhD/GkurpZSGaJA+9GPaeQyTROb9D4rBrqtQj03n45Q X-Received: by 2002:a17:907:3e96:b0:6e8:aeb9:4f91 with SMTP id hs22-20020a1709073e9600b006e8aeb94f91mr18938025ejc.314.1650934143304; Mon, 25 Apr 2022 17:49:03 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1650934143; cv=none; d=google.com; s=arc-20160816; b=tBYOQb/XDXx51AfU1g7TrXMP5Sws7HsTwMLvpn1uzeWTmvNLsjyDc13cP0gHQbUYXI AAAJmccYMAWr0LW0GC8P3RJ/AhAvsESxIknHeI9qrFLDJqAcV3Usw0tiO1XY5EOkwXWC VHGeC/DaScJMYuELGmMMGtw3J25atBfw0B6OPgGGQxVKdCTbtWVKykewXbZNIWYTgkQ1 M5N+rF6XwpuWQwAavVBIPvTtnL/qG5z/+i35WBvsqRcbtToxa0Zl2ktg7iHzX0C3W2eG 1vpey/YgD15x07DE040vCU9hF41c3IyM/ajhpByKkED2HMHwt71PAJxPVnbBiaMU2CYY GCxA== 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=3D/48VQENOnSlSpNLDthc2JNrwKESJgr2gi9ea5PG60=; b=acqbPgeGBV0R8/RVyD2FL5DtY+zAPU21wumaraRdxIpwfty0AZv+D7Yoo1M3U3h1mh 2Bc+UOhDR0xFpehAEOlQMAAJBQI+hc8prKAr8bd+IsgPhH0AeMZnqAig5NPm5Ru9j9uG Iy1QbhMjiYcHZ536Z3N9w3FESeyQ48jVJNNyzs1SzYCTJKSFuwT8GZN72NkxNEBTrxhU LC8/rYNcyDczUg9cm1d2xYpoqyiruHjRnyLI1S6t42NHif98KKyt2kCmuDWPFw/m1P5o BtnOOk8xu6iNvaa6ddfghVjAwzynwXHJuDP3TRr81K4VYgBy9Uv47G0W+t4looZvuid5 1zJQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=OcBjCD6M; 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 y10-20020a056402270a00b00423efe14d9bsi14474196edd.575.2022.04.25.17.48.40; Mon, 25 Apr 2022 17:49:03 -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=OcBjCD6M; 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 S244031AbiDYRuh (ORCPT + 99 others); Mon, 25 Apr 2022 13:50:37 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46944 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S244019AbiDYRuf (ORCPT ); Mon, 25 Apr 2022 13:50:35 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 1C1061C901 for ; Mon, 25 Apr 2022 10:47:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1650908850; 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=3D/48VQENOnSlSpNLDthc2JNrwKESJgr2gi9ea5PG60=; b=OcBjCD6MSGM2q7IjdXWBumqNP2jPy2A/uIlMJUvbAUZ6zFO/QaAMHG3hWShFrGNM9r1c0g yWVV3g4g/r4sc1YY3SN+BCwxk5ALRwQgn4rE2OJGadeM6Nk4ljBZQ+VUQEkhMoJkTvaj0w wR7RwH6/ytBq7q7/ZJBnYEJuLCWzq/Y= 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-656-pFzPbk9MO0m3sVwH1Ss_MA-1; Mon, 25 Apr 2022 13:47:25 -0400 X-MC-Unique: pFzPbk9MO0m3sVwH1Ss_MA-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 35DEE800B28; Mon, 25 Apr 2022 17:47:24 +0000 (UTC) Received: from dhcp-27-174.brq.redhat.com (unknown [10.40.193.11]) by smtp.corp.redhat.com (Postfix) with SMTP id 272C540CF910; Mon, 25 Apr 2022 17:47:20 +0000 (UTC) Received: by dhcp-27-174.brq.redhat.com (nbSMTP-1.00) for uid 1000 oleg@redhat.com; Mon, 25 Apr 2022 19:47:23 +0200 (CEST) Date: Mon, 25 Apr 2022 19:47:20 +0200 From: Oleg Nesterov To: Peter Zijlstra Cc: rjw@rjwysocki.net, mingo@kernel.org, vincent.guittot@linaro.org, dietmar.eggemann@arm.com, rostedt@goodmis.org, mgorman@suse.de, ebiederm@xmission.com, bigeasy@linutronix.de, Will Deacon , linux-kernel@vger.kernel.org, tj@kernel.org, linux-pm@vger.kernel.org Subject: Re: [PATCH v2 2/5] sched,ptrace: Fix ptrace_check_attach() vs PREEMPT_RT Message-ID: <20220425174719.GB12412@redhat.com> References: <20220421150248.667412396@infradead.org> <20220421150654.817117821@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220421150654.817117821@infradead.org> 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/21, Peter Zijlstra wrote: > > @@ -2225,7 +2238,7 @@ static int ptrace_stop(int exit_code, in > * schedule() will not sleep if there is a pending signal that > * can awaken the task. > */ > - current->jobctl |= JOBCTL_TRACED; > + current->jobctl |= JOBCTL_TRACED | JOBCTL_TRACED_QUIESCE; > set_special_state(TASK_TRACED); OK, this looks wrong. I actually mean the previous patch which sets JOBCTL_TRACED. The problem is that the tracee can be already killed, so that fatal_signal_pending(current) is true. In this case we can't rely on signal_wake_up_state() which should clear JOBCTL_TRACED, or the callers of ptrace_signal_wake_up/etc which clear this flag by hand. In this case schedule() won't block and ptrace_stop() will leak JOBCTL_TRACED. Unless I missed something. We could check fatal_signal_pending() and damn! this is what I think ptrace_stop() should have done from the very beginning. But for now I'd suggest to simply clear this flag before return, along with DELAY_WAKEKILL and LISTENING. > current->jobctl &= ~JOBCTL_LISTENING; > + current->jobctl &= ~JOBCTL_DELAY_WAKEKILL; current->jobctl &= ~(~JOBCTL_TRACED | JOBCTL_DELAY_WAKEKILL | JOBCTL_LISTENING); Oleg.