Received: by 2002:a6b:fb09:0:0:0:0:0 with SMTP id h9csp5034044iog; Wed, 22 Jun 2022 10:32:55 -0700 (PDT) X-Google-Smtp-Source: AGRyM1uyUE4f4rEfbK/0ueV3EkJmNf2wx5pUEFB+QNCaeNT4alUoYGWvB46TxFZaf/YQKhGeiiOi X-Received: by 2002:a17:907:8a13:b0:707:194c:30df with SMTP id sc19-20020a1709078a1300b00707194c30dfmr4370255ejc.154.1655919175432; Wed, 22 Jun 2022 10:32:55 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1655919175; cv=none; d=google.com; s=arc-20160816; b=CmiR3u39YxY9fhwRNgBbbPP+9MriDvJSTunD4Na3iaPF0q2HwKF/krNlVS3+8g+ZNe jRI4wy0Pu805qgRS5rj0J57k81bnVlKgU69jiR1Y6yJGQSKu+w1jFk60MON1ZnyTV4bh JcXc8MfYKAZF1sJAfbyFbhUkqYIdF+tDqpkdo59Qi0G+T8HWhn+TxMp754KvXtjBgjHu 2jh/60kDYpAOCrrlpJ4CUj9hd7OMW1F9yogVuwthtZXgZ2RHFQBSR6cpiDNAWdZ5B+/c wjrhuZyrKeL9d702rP2gJ+o218BRIdls56+M7AI+6wEtFKDbKun9cad5rAPcjP5yzU6Z rumw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:subject:mime-version:user-agent:message-id :in-reply-to:date:references:cc:to:from; bh=zOVCWmo4/0ia/j2jk3A9vxkmnhDXqqnCXQNYIBl5e8w=; b=PtrKxxePOrMo6rfQfMtFUOJgNSauW2wjPl06THERQw75dW3EpbP0WWAxtQ0fre11eu 4DO7XEkr0IE+sNQXW4RBawHlKV6nLATLGuD0yYvIFaDSSPkeUwvHixMHzQw+s5LGP4no lSpJRaXWK/TUIfJfCiBeqRyZtOJX4icIBfG7JBySEWxCPW/8ce949KFLOYeuR5bmCxC8 6ZSi+J561LUCSVwzuuDmqpcrzGMJxKNrnAg4q96m0r9Qj6fzhiYJjCDsa170vEklJ1ps AQ9CBMX2p1eHTu9od6gG3137DVPW6nL64dZYigGcQWiADIELbPABNgEflxN+0G7KCoTj EjaA== ARC-Authentication-Results: i=1; mx.google.com; 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=fail (p=NONE sp=NONE dis=NONE) header.from=xmission.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id y1-20020a170906518100b00722b1057bfdsi3241222ejk.592.2022.06.22.10.32.28; Wed, 22 Jun 2022 10:32:55 -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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=xmission.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1357542AbiFVQoR (ORCPT + 99 others); Wed, 22 Jun 2022 12:44:17 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46416 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236563AbiFVQoP (ORCPT ); Wed, 22 Jun 2022 12:44:15 -0400 Received: from out03.mta.xmission.com (out03.mta.xmission.com [166.70.13.233]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6FD8333E19 for ; Wed, 22 Jun 2022 09:44:14 -0700 (PDT) Received: from in01.mta.xmission.com ([166.70.13.51]:57132) by out03.mta.xmission.com with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from ) id 1o43Sd-00AWLN-1r; Wed, 22 Jun 2022 10:44:11 -0600 Received: from ip68-227-174-4.om.om.cox.net ([68.227.174.4]:57362 helo=email.froward.int.ebiederm.org.xmission.com) by in01.mta.xmission.com with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from ) id 1o43Sa-001XTg-Lr; Wed, 22 Jun 2022 10:44:10 -0600 From: "Eric W. Biederman" To: Oleg Nesterov Cc: linux-kernel@vger.kernel.org, mingo@kernel.org, bigeasy@linutronix.de, Peter Zijlstra , Jann Horn , Kees Cook , Alexander Gordeev , Robert O'Callahan , Kyle Huey , Keno Fischer References: <20220421150248.667412396@infradead.org> <20220421150654.817117821@infradead.org> <87czhap9dy.fsf@email.froward.int.ebiederm.org> <878rrrh32q.fsf_-_@email.froward.int.ebiederm.org> <87k0b7v9yk.fsf_-_@email.froward.int.ebiederm.org> <87k0b0apne.fsf_-_@email.froward.int.ebiederm.org> <87a6bv6dl6.fsf_-_@email.froward.int.ebiederm.org> Date: Wed, 22 Jun 2022 11:43:37 -0500 In-Reply-To: <87a6bv6dl6.fsf_-_@email.froward.int.ebiederm.org> (Eric W. Biederman's message of "Thu, 05 May 2022 13:25:57 -0500") Message-ID: <87r13gd4xy.fsf_-_@email.froward.int.ebiederm.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-XM-SPF: eid=1o43Sa-001XTg-Lr;;;mid=<87r13gd4xy.fsf_-_@email.froward.int.ebiederm.org>;;;hst=in01.mta.xmission.com;;;ip=68.227.174.4;;;frm=ebiederm@xmission.com;;;spf=softfail X-XM-AID: U2FsdGVkX1+HUrQnJ1mzH6gsmI5jzL3UyqNu9wsYCv8= X-SA-Exim-Connect-IP: 68.227.174.4 X-SA-Exim-Mail-From: ebiederm@xmission.com X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-DCC: XMission; sa07 1397; Body=1 Fuz1=1 Fuz2=1 X-Spam-Combo: ****;Oleg Nesterov X-Spam-Relay-Country: X-Spam-Timing: total 1777 ms - load_scoreonly_sql: 0.08 (0.0%), signal_user_changed: 12 (0.7%), b_tie_ro: 10 (0.6%), parse: 1.36 (0.1%), extract_message_metadata: 3.8 (0.2%), get_uri_detail_list: 0.82 (0.0%), tests_pri_-1000: 4.2 (0.2%), tests_pri_-950: 1.32 (0.1%), tests_pri_-900: 1.05 (0.1%), tests_pri_-90: 78 (4.4%), check_bayes: 77 (4.3%), b_tokenize: 5 (0.3%), b_tok_get_all: 5 (0.3%), b_comp_prob: 1.95 (0.1%), b_tok_touch_all: 61 (3.4%), b_finish: 0.85 (0.0%), tests_pri_0: 1603 (90.2%), check_dkim_signature: 0.90 (0.1%), check_dkim_adsp: 3.5 (0.2%), poll_dns_idle: 0.80 (0.0%), tests_pri_10: 5 (0.3%), tests_pri_500: 56 (3.1%), rewrite_mail: 0.00 (0.0%) Subject: [PATCH 0/3] ptrace: Stop supporting SIGKILL for PTRACE_EVENT_EXIT X-SA-Exim-Version: 4.2.1 (built Sat, 08 Feb 2020 21:53:50 +0000) X-SA-Exim-Scanned: Yes (on in01.mta.xmission.com) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Recently I had a conversation where it was pointed out to me that SIGKILL sent to a tracee stropped in PTRACE_EVENT_EXIT is quite difficult for a tracer to handle. Keeping SIGKILL working for anything after the process has been killed is also a real pain from an implementation point of view. So I am attempting to remove this wart in the userspace API and see if anyone cares. Eric W. Biederman (3): signal: Ensure SIGNAL_GROUP_EXIT gets set in do_group_exit signal: Guarantee that SIGNAL_GROUP_EXIT is set on process exit signal: Drop signals received after a fatal signal has been processed fs/coredump.c | 2 +- include/linux/sched/signal.h | 1 + kernel/exit.c | 20 +++++++++++++++++++- kernel/fork.c | 2 ++ kernel/signal.c | 3 ++- 5 files changed, 25 insertions(+), 3 deletions(-) Eric