From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5BC17C433FE for ; Tue, 2 Nov 2021 18:22:31 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 43EA560F58 for ; Tue, 2 Nov 2021 18:22:31 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230256AbhKBSZF (ORCPT ); Tue, 2 Nov 2021 14:25:05 -0400 Received: from out02.mta.xmission.com ([166.70.13.232]:57560 "EHLO out02.mta.xmission.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230230AbhKBSZE (ORCPT ); Tue, 2 Nov 2021 14:25:04 -0400 Received: from in02.mta.xmission.com ([166.70.13.52]:38068) by out02.mta.xmission.com with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from ) id 1mhyQW-00AJ67-Tr; Tue, 02 Nov 2021 12:22:28 -0600 Received: from ip68-227-160-95.om.om.cox.net ([68.227.160.95]:37228 helo=email.xmission.com) by in02.mta.xmission.com with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from ) id 1mhyQV-00EizZ-01; Tue, 02 Nov 2021 12:22:28 -0600 From: ebiederm@xmission.com (Eric W. Biederman) To: Kees Cook Cc: Andrea Righi , Shuah Khan , Alexei Starovoitov , Andy Lutomirski , Will Drewry , linux-kselftest@vger.kernel.org, bpf@vger.kernel.org, linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org References: <202110280955.B18CB67@keescook> <878rydm56l.fsf@disp2133> <202110281136.5CE65399A7@keescook> <8735okls76.fsf@disp2133> <202110290755.451B036CE9@keescook> Date: Tue, 02 Nov 2021 13:22:19 -0500 In-Reply-To: <202110290755.451B036CE9@keescook> (Kees Cook's message of "Fri, 29 Oct 2021 07:58:02 -0700") Message-ID: <87y2665sf8.fsf@disp2133> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-XM-SPF: eid=1mhyQV-00EizZ-01;;;mid=<87y2665sf8.fsf@disp2133>;;;hst=in02.mta.xmission.com;;;ip=68.227.160.95;;;frm=ebiederm@xmission.com;;;spf=neutral X-XM-AID: U2FsdGVkX1/dOLwlXmVI7aCH/YYnczuKSEUIah1vXvg= X-SA-Exim-Connect-IP: 68.227.160.95 X-SA-Exim-Mail-From: ebiederm@xmission.com Subject: Re: selftests: seccomp_bpf failure on 5.15 X-SA-Exim-Version: 4.2.1 (built Sat, 08 Feb 2020 21:53:50 +0000) X-SA-Exim-Scanned: Yes (on in02.mta.xmission.com) Precedence: bulk List-ID: X-Mailing-List: bpf@vger.kernel.org Kees Cook writes: > On Thu, Oct 28, 2021 at 05:06:53PM -0500, Eric W. Biederman wrote: >> Kees Cook writes: >> >> > On Thu, Oct 28, 2021 at 12:26:26PM -0500, Eric W. Biederman wrote: >> >> Is it a problem that the debugger can see the signal if the process does >> not? > > Right, I'm trying to understand that too. However, my neighbor just lost > power. :| > > What I was in the middle of checking was what ptrace "sees" going > through a fatal SIGSYS; my initial debugging attempts were weird. Kees have you regained power and had a chance to see my SA_IMMUTABLE patch? Does what I implemented seem like it will work for you? I think it is a solid and simple solution to a pair of problems with my change to use the ordinary coredump path for seccomp. But I would very much love to hear it seems reasonable to you, as you were looking at the problem as well. Eric