Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp3653481yba; Tue, 23 Apr 2019 07:27:07 -0700 (PDT) X-Google-Smtp-Source: APXvYqxx4KdqF+jPLqvlhNd9+OeZ+9ppTTcFC5fZ3ziZA5VnIXmw6ZRfgPvxfKpmHSZg6nnRaONI X-Received: by 2002:a63:550d:: with SMTP id j13mr25208251pgb.18.1556029627897; Tue, 23 Apr 2019 07:27:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1556029627; cv=none; d=google.com; s=arc-20160816; b=RtkV5fn7nhx0rRBEddqYOKv/wVj9K7rUKBP2ggJ8A9avlzfAJxcPXo0vWbmhPmEaMs P34MgwbmPTAatSwiallNkISOguA5Oc5ZzZm+RunoPbYqLDUMS6V7ZV1IKk2iQGDhb5hS 6VRlt919Hpq6ZA82QLQk7zpzRPWhFNT6yl91ze28bkqAe37ZIWMqQW5HAUfNREvMInfe HYVXHE24XvlZgbGR3IqsQ2r4xvnAlMiUKv1SLn+yLAJc+stXk5iTDNcFiKievvXepTve Bl+HVxw3wqW4sMYSAoed4nfjkd4N2NYHKfXUndueeO6Nu7VKT6hTSnT54pOJXGMrrJTE csRg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:content-transfer-encoding :content-language:accept-language:message-id:date:thread-index :thread-topic:subject:cc:to:from; bh=ZK9L3AbAZEn3q7zYkC+PxLSmXoG66bldg6ZukTdqQ2k=; b=NjrtM0sH0SJ7MTAyI8McLIezFDxtCSLtH0uN9fNPsk8aXAcorY6sMxmqPkQSAVs5Ns OkcUNA4hCb4jRQY6+NUyHucaB9JWMBuExU+3iSQ0jcijIBgQyruZwhZ52HcvpDI+kVYH AM75M3DllD0HKC30M9yIKKlkkae9vZD5v9BMOZGrTJ09XlmJx17KJ8urCalJ9uqtH6dE gnA7FF6Xf2OIGJU700VYLjWr9AvVQpoo1M3PdTm7Oyc4dxyRFxeCcn8sJu8oSLz+Za1O S+/wTwU9ZbGkGOnXWwS30/BtH43QnMg4clnGiyL+FhM0MC1tShDjiVuFJ5z56Cf7+HT8 DuMw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x5si17676281pfo.84.2019.04.23.07.26.52; Tue, 23 Apr 2019 07:27:07 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728177AbfDWOZN convert rfc822-to-8bit (ORCPT + 99 others); Tue, 23 Apr 2019 10:25:13 -0400 Received: from szxga02-in.huawei.com ([45.249.212.188]:2993 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727305AbfDWOZN (ORCPT ); Tue, 23 Apr 2019 10:25:13 -0400 Received: from dggemi402-hub.china.huawei.com (unknown [172.30.72.55]) by Forcepoint Email with ESMTP id 07446692A14290045861; Tue, 23 Apr 2019 22:25:09 +0800 (CST) Received: from DGGEMI530-MBX.china.huawei.com ([169.254.7.146]) by dggemi402-hub.china.huawei.com ([10.3.17.135]) with mapi id 14.03.0415.000; Tue, 23 Apr 2019 22:25:07 +0800 From: weizhenliang To: Greg KH CC: "ebiederm@xmission.com" , "oleg@redhat.com" , "colona@arista.com" , "akpm@linux-foundation.org" , "christian@brauner.io" , "arnd@arndb.de" , "tglx@linutronix.de" , "deepa.kernel@gmail.com" , "linux-kernel@vger.kernel.org" , "stable@vger.kernel.org" Subject: Re: [PATCH v3] signal: trace_signal_deliver when signal_group_exit Thread-Topic: [PATCH v3] signal: trace_signal_deliver when signal_group_exit Thread-Index: AdT53lFy7/5lmntORAqlla0EhT1kYw== Date: Tue, 23 Apr 2019 14:25:07 +0000 Message-ID: Accept-Language: en-US Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.40.99.192] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 04/23, Greg KH wrote: >On Mon, Apr 22, 2019 at 10:59:50PM +0800, Zhenliang Wei wrote: >> In the fixes commit, removing SIGKILL from each thread signal mask and >> executing "goto fatal" directly will skip the call to >> "trace_signal_deliver". At this point, the delivery tracking of the >> SIGKILL signal will be inaccurate. >> >> Therefore, we need to add trace_signal_deliver before "goto fatal" >> after executing sigdelset. >> >> Note: The action[SIGKILL] must be SIG_DFL, and SEND_SIG_NOINFO matches >> the fact that SIGKILL doesn't have any info. >> >> Acked-by: Christian Brauner >> Fixes: cf43a757fd4944 ("signal: Restore the stop PTRACE_EVENT_EXIT") >> Signed-off-by: Zhenliang Wei >> --- >> kernel/signal.c | 1 + >> 1 file changed, 1 insertion(+) >> >> diff --git a/kernel/signal.c b/kernel/signal.c index >> 227ba170298e..0f69ada376ef 100644 >> --- a/kernel/signal.c >> +++ b/kernel/signal.c >> @@ -2441,6 +2441,7 @@ bool get_signal(struct ksignal *ksig) >> if (signal_group_exit(signal)) { >> ksig->info.si_signo = signr = SIGKILL; >> sigdelset(¤t->pending.signal, SIGKILL); >> + trace_signal_deliver(SIGKILL, SEND_SIG_NOINFO, SIG_DFL); >> recalc_sigpending(); >> goto fatal; >> } >> -- >> 2.14.1.windows.1 >> >> > > > >This is not the correct way to submit patches for inclusion in the stable kernel tree. Please read: > https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html >for how to do this properly. > > Thans for your reply, is that mean I still need to add tags Cc: stable@vger.kernel.org if I want to submit this patch to the stable kernel tree? Is my understanding correct or missing? Wei