From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757551AbdACF5o (ORCPT ); Tue, 3 Jan 2017 00:57:44 -0500 Received: from mail.kernel.org ([198.145.29.136]:34598 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757166AbdACF5i (ORCPT ); Tue, 3 Jan 2017 00:57:38 -0500 MIME-Version: 1.0 In-Reply-To: <1483375990-14948-1-git-send-email-tyhicks@canonical.com> References: <1483375990-14948-1-git-send-email-tyhicks@canonical.com> From: Andy Lutomirski Date: Mon, 2 Jan 2017 21:57:15 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH 0/2] Begin auditing SECCOMP_RET_ERRNO return actions To: Tyler Hicks Cc: Paul Moore , Eric Paris , Kees Cook , Will Drewry , linux-audit@redhat.com, "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jan 2, 2017 at 8:53 AM, Tyler Hicks wrote: > This patch set creates the basis for auditing information specific to a given > seccomp return action and then starts auditing SECCOMP_RET_ERRNO return > actions. The audit messages for SECCOMP_RET_ERRNO return actions include the > errno value that will be returned to userspace. > Not that I'm opposed to the idea, but what's the intended purpose?