Received: by 10.192.165.148 with SMTP id m20csp145501imm; Thu, 19 Apr 2018 18:10:02 -0700 (PDT) X-Google-Smtp-Source: AIpwx49sS47+p8xIxAyUVOsz9GabeKRR6jxw0Yu8Iypd9MAncdCwQBoyY9/5YCSqlIfnN6Td5MOS X-Received: by 10.99.174.73 with SMTP id e9mr6703762pgp.38.1524186602854; Thu, 19 Apr 2018 18:10:02 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1524186602; cv=none; d=google.com; s=arc-20160816; b=gW+Icy6In58VkU8w1duELSV1TNP5yEX2hQvER0lBnatJlwLJpCThNr6ECxVywIbFrH liiHyLgVMjNsF/N6LNidpmadegmtusHTNI+zfZ9QWM3AKaru5vNFMAxHEg5SfNoE0oxu +AnwndbEtBoW+S4EnqSP1TfNAHOnP1jH4sCwsZMc3D/5PnKM8m2SKeaQ8z43KKY43dDm WxmQOCVycxl318pJ6SpTBClae53JqyPnNzF/JVE11vrfBkzBcCZZd/02Cdl1ANdX8/hl 8Q+5Yx7c9VXcu81OwYbvrd5k49JfkFeRvbEOJrmfyZKI6P6qT7LNscazVRu2ZupF/Eye zWOw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:subject:references:in-reply-to:message-id :date:cc:to:from:arc-authentication-results; bh=+rEAcr4sw97p67yVFsKwBNMLMgZ8HC+89OKo8gRt+dU=; b=KvSAt9S3xDFcp1b5O7dyDtErVpzjPtQAHOscdXAPrPEGCXVjxXEHQU7SG1fqh3MOrv /E2byek7utc2qoZZnSI1stjvOHzkRWdm1sET7zskFyfgGgkMAp9RwUhHC4jowmqoF0HP HSKXCT8Wc1gLOs7vgrPQvW3XUv4Cj2namHKaTxlQh4w6vssXlg0+NQXywRJjfZDmfpFz Q0gMXX9FwxYfHGifOEpz70kzyTjJH+4toGz+Sf9BpviKd++NDCYsdfVfiX9u0GEYLOXX h+7u11MNLStZ8I+seOXnjy7I3ln6Efy8XPdrXPKRycs6DWFpVfowt/jhhVgHOQSRnwcF d86w== 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 t64si4060500pgc.160.2018.04.19.18.09.48; Thu, 19 Apr 2018 18:10:02 -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 S1754177AbeDTBH3 (ORCPT + 99 others); Thu, 19 Apr 2018 21:07:29 -0400 Received: from out03.mta.xmission.com ([166.70.13.233]:50135 "EHLO out03.mta.xmission.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753992AbeDTBH1 (ORCPT ); Thu, 19 Apr 2018 21:07:27 -0400 Received: from in01.mta.xmission.com ([166.70.13.51]) by out03.mta.xmission.com with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.87) (envelope-from ) id 1f9KWM-0006oK-HM; Thu, 19 Apr 2018 19:07:26 -0600 Received: from [97.119.174.25] (helo=x220.int.ebiederm.org) by in01.mta.xmission.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.87) (envelope-from ) id 1f9KW6-00014u-SB; Thu, 19 Apr 2018 19:07:26 -0600 From: "Eric W. Biederman" To: linux-arch@vger.kernel.org Cc: linux-kernel@vger.kernel.org, linux-api@vger.kernel.org, "Eric W. Biederman" Date: Thu, 19 Apr 2018 20:03:59 -0500 Message-Id: <20180420010408.24438-8-ebiederm@xmission.com> X-Mailer: git-send-email 2.14.1 In-Reply-To: <878t9ilmhv.fsf@xmission.com> References: <878t9ilmhv.fsf@xmission.com> X-XM-SPF: eid=1f9KW6-00014u-SB;;;mid=<20180420010408.24438-8-ebiederm@xmission.com>;;;hst=in01.mta.xmission.com;;;ip=97.119.174.25;;;frm=ebiederm@xmission.com;;;spf=neutral X-XM-AID: U2FsdGVkX18uSgI+mxwhJAKd5brXS8cDvuLbLZjNbf0= X-SA-Exim-Connect-IP: 97.119.174.25 X-SA-Exim-Mail-From: ebiederm@xmission.com X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on sa07.xmission.com X-Spam-Level: ******* X-Spam-Status: No, score=7.5 required=8.0 tests=ALL_TRUSTED,BAYES_50,DCC_CHECK, TR_Symld_Words,T_TooManySym_01,T_XMDrugObfuBody_04,XMNoVowels,XMSubLong autolearn=disabled version=3.4.1 X-Spam-Report: * -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP * 0.7 XMSubLong Long Subject * 1.5 XMNoVowels Alpha-numberic number with no vowels * 1.5 TR_Symld_Words too many words that have symbols inside * 0.8 BAYES_50 BODY: Bayes spam probability is 40 to 60% * [score: 0.4990] * 3.0 DCC_CHECK Listed in DCC (http://rhyolite.com/anti-spam/dcc/) * [sa07 1397; Body=1 Fuz1=1 Fuz2=many] * 0.0 T_TooManySym_01 4+ unique symbols in subject * 1.0 T_XMDrugObfuBody_04 obfuscated drug references X-Spam-DCC: XMission; sa07 1397; Body=1 Fuz1=1 Fuz2=many X-Spam-Combo: *******;linux-arch@vger.kernel.org X-Spam-Relay-Country: X-Spam-Timing: total 15023 ms - load_scoreonly_sql: 0.04 (0.0%), signal_user_changed: 2.8 (0.0%), b_tie_ro: 1.99 (0.0%), parse: 0.95 (0.0%), extract_message_metadata: 11 (0.1%), get_uri_detail_list: 1.57 (0.0%), tests_pri_-1000: 2.8 (0.0%), tests_pri_-950: 1.22 (0.0%), tests_pri_-900: 1.00 (0.0%), tests_pri_-400: 16 (0.1%), check_bayes: 15 (0.1%), b_tokenize: 4.8 (0.0%), b_tok_get_all: 4.9 (0.0%), b_comp_prob: 1.67 (0.0%), b_tok_touch_all: 2.3 (0.0%), b_finish: 0.63 (0.0%), tests_pri_0: 127 (0.8%), check_dkim_signature: 0.42 (0.0%), check_dkim_adsp: 2.5 (0.0%), tests_pri_500: 14858 (98.9%), poll_dns_idle: 14849 (98.8%), rewrite_mail: 0.00 (0.0%) Subject: [REVIEW][PATCH 08/17] signal: Stop special casing TRAP_FIXME and FPE_FIXME in siginfo_layout X-Spam-Flag: No X-SA-Exim-Version: 4.2.1 (built Thu, 05 May 2016 13:38:54 -0600) X-SA-Exim-Scanned: Yes (on in01.mta.xmission.com) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org After more experience with the cases where no one the si_code of 0 is used both as a signal specific si_code, and as SI_USER it appears that no one cares about the signal specific si_code case and the good solution is to just fix the architectures by using a different si_code. In none of the conversations has anyone even suggested that anything depends on the signal specific redefinition of SI_USER. There are at least test cases that care when si_code as 0 does not work as si_user. So make things simple and keep the generic code from introducing problems by removing the special casing of TRAP_FIXME and FPE_FIXME. This will ensure the generic case of sending a signal with kill will always set SI_USER and work. The architecture specific, and signal specific overloads that set si_code to 0 will now have problems with signalfd and the 32bit compat versions of siginfo copying. At least until they are fixed. Signed-off-by: "Eric W. Biederman" --- kernel/signal.c | 9 --------- 1 file changed, 9 deletions(-) diff --git a/kernel/signal.c b/kernel/signal.c index d56f4d496c89..fc82d2c0918f 100644 --- a/kernel/signal.c +++ b/kernel/signal.c @@ -2835,15 +2835,6 @@ enum siginfo_layout siginfo_layout(int sig, int si_code) layout = SIL_POLL; else if (si_code < 0) layout = SIL_RT; - /* Tests to support buggy kernel ABIs */ -#ifdef TRAP_FIXME - if ((sig == SIGTRAP) && (si_code == TRAP_FIXME)) - layout = SIL_FAULT; -#endif -#ifdef FPE_FIXME - if ((sig == SIGFPE) && (si_code == FPE_FIXME)) - layout = SIL_FAULT; -#endif } return layout; } -- 2.14.1