From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750744AbdAVWKn (ORCPT ); Sun, 22 Jan 2017 17:10:43 -0500 Received: from namei.org ([65.99.196.166]:33921 "EHLO namei.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750703AbdAVWKm (ORCPT ); Sun, 22 Jan 2017 17:10:42 -0500 Date: Mon, 23 Jan 2017 09:10:25 +1100 (AEDT) From: James Morris To: Kees Cook cc: Mike Frysinger , James Morris , LKML , Andy Lutomirski , Will Drewry , Mike Frysinger Subject: Re: [PATCH] seccomp: dump core when using SECCOMP_RET_KILL In-Reply-To: Message-ID: References: <20170120042857.18953-1-vapier@gentoo.org> User-Agent: Alpine 2.20 (LRH 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 20 Jan 2017, Kees Cook wrote: > Yup, I think this is fine. The additional kernel code executed before > the do_exit() is relatively limited, and is equivalent to leaving > kill(self, SIGSEGV) exposed in a seccomp filter. Setting an RLIMIT is > also sufficient to block the core generation, so really paranoid > environments can still do that. > > The forwarded ack stands: > > Acked-by: Kees Cook > > James, can you add this to your tree? Mike, please resend the patch, I don't have it. -- James Morris