Received: by 2002:a25:86ce:0:0:0:0:0 with SMTP id y14csp1568930ybm; Thu, 23 May 2019 03:19:25 -0700 (PDT) X-Google-Smtp-Source: APXvYqwjydJEiTDGEGEYreNaRA6oO3YT2UdmjVlWSa6vr8G8Th+ewFDnko3wwdgQQzWkY31zPOqA X-Received: by 2002:a63:db4e:: with SMTP id x14mr81572779pgi.119.1558606764838; Thu, 23 May 2019 03:19:24 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558606764; cv=none; d=google.com; s=arc-20160816; b=poUAB6vp7GmfgLLw7OB+NFGtA+bhSArZPIkbaOJg5yZWbE1JEOcMQioYc8G2mSdWKb UoXV74VIDi5FEj5ka8ciYoqRH10AqQlDFfCABJSs0Ufq2GX5xJ4D+my8JmdMbozNu+L9 nNKj8oIMmhwMUzvbkpCT4yXUIyQAJZnjM8TSWESyYiRlbZ8/B0c6zZz98yKyRmxapNZG CW2ePfK9XdqTeQ5E8rK/Rz9I0yT839T3wBVNv/4uIV8pC268VfT6dZNfqvb6nPEBfwlU 2tD/9RVYLlbj0DfkvDU4blpkvktxbYOad7u/yIet8yhXcyHCOIAEa1pW2l4wMTn/bWpV HcCQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=1+QgKz+/gSo0buO2KgH29AKK6799UFM7TrmgAGbymnY=; b=SZdM8VyUrNze3GAxqXghD+FO0+pqiWPU8tMqa/voluzNdosyvHzlTC+Yhp0rd4pH8Q i7uv6/b9f4x2XEtvwv5T+NqfmaBwg+DAm0OMyKeg7dcrlUN93LLmrBsnIfvGRFYDPe+A FB5X7PN1SEt49T6HaQ5TfkluxAS6rs5YV3ayIBM7Zxfwyp0LNlDctDB5YhHvoRgEafgT 78TVb4PljnWBk529Ar2UE6tpN2sMHd8GuxRSiBjgB+dJOKuHUZwEoJATMnj7zIjvAZKI LFQNithjC/lbhWIQcX7t0Y60evzWWFki76or+75DzqzBza+htfs1QRDdr2SQ2aKfxA+p m/yw== 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 cp14si30395423plb.183.2019.05.23.03.19.09; Thu, 23 May 2019 03:19:24 -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 S1730404AbfEWKRH (ORCPT + 99 others); Thu, 23 May 2019 06:17:07 -0400 Received: from foss.arm.com ([217.140.101.70]:42332 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726846AbfEWKRG (ORCPT ); Thu, 23 May 2019 06:17:06 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 36DF9341; Thu, 23 May 2019 03:17:06 -0700 (PDT) Received: from fuggles.cambridge.arm.com (usa-sjc-imap-foss1.foss.arm.com [10.72.51.249]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id D34083F718; Thu, 23 May 2019 03:17:04 -0700 (PDT) Date: Thu, 23 May 2019 11:17:02 +0100 From: Will Deacon To: "Eric W. Biederman" Cc: linux-kernel@vger.kernel.org, Linux Containers , Oleg Nesterov , linux-arch@vger.kernel.org, Dave Martin , James Morse Subject: Re: [REVIEW][PATCH 03/26] signal/arm64: Use force_sig not force_sig_fault for SIGKILL Message-ID: <20190523101702.GG26646@fuggles.cambridge.arm.com> References: <20190523003916.20726-1-ebiederm@xmission.com> <20190523003916.20726-4-ebiederm@xmission.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190523003916.20726-4-ebiederm@xmission.com> User-Agent: Mutt/1.11.1+86 (6f28e57d73f2) () Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, May 22, 2019 at 07:38:53PM -0500, Eric W. Biederman wrote: > It really only matters to debuggers but the SIGKILL does not have any > si_codes that use the fault member of the siginfo union. Correct this > the simple way and call force_sig instead of force_sig_fault when the > signal is SIGKILL. > > Cc: stable@vger.kernel.org > Cc: Dave Martin > Cc: James Morse > Cc: Will Deacon > Fixes: af40ff687bc9 ("arm64: signal: Ensure si_code is valid for all fault signals") > Signed-off-by: "Eric W. Biederman" > --- > arch/arm64/kernel/traps.c | 5 +++++ > 1 file changed, 5 insertions(+) > > diff --git a/arch/arm64/kernel/traps.c b/arch/arm64/kernel/traps.c > index ade32046f3fe..0feb17bdcaa0 100644 > --- a/arch/arm64/kernel/traps.c > +++ b/arch/arm64/kernel/traps.c > @@ -282,6 +282,11 @@ void arm64_notify_die(const char *str, struct pt_regs *regs, > current->thread.fault_address = 0; > current->thread.fault_code = err; > > + if (signo == SIGKILL) { > + arm64_show_signal(signo, str); > + force_sig(signo, current); > + return; > + } I know it's a bit of a misnomer, but I'd rather do this check inside arm64_force_sig_fault, since I think we have other callers (e.g. do_bad_area()) which also blindly pass in SIGKILL here. We could rename the thing if necessary. Will