From mboxrd@z Thu Jan  1 00:00:00 1970
From: Steve Grubb <sgrubb@redhat.com>
Subject: SECCOMP event results
Date: Tue, 11 Apr 2017 17:27:16 -0400
Message-ID: <2280482.zxXSvVIUhu@x2>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <linux-audit-bounces@redhat.com>
Received: from x2.localnet (ovpn-124-21.rdu2.redhat.com [10.10.124.21])
	by smtp.corp.redhat.com (Postfix) with ESMTPS id 128AB62926
	for <linux-audit@redhat.com>; Tue, 11 Apr 2017 21:27:17 +0000 (UTC)
List-Unsubscribe: <https://www.redhat.com/mailman/options/linux-audit>,
	<mailto:linux-audit-request@redhat.com?subject=unsubscribe>
List-Archive: <https://www.redhat.com/archives/linux-audit>
List-Post: <mailto:linux-audit@redhat.com>
List-Help: <mailto:linux-audit-request@redhat.com?subject=help>
List-Subscribe: <https://www.redhat.com/mailman/listinfo/linux-audit>,
	<mailto:linux-audit-request@redhat.com?subject=subscribe>
Sender: linux-audit-bounces@redhat.com
Errors-To: linux-audit-bounces@redhat.com
To: linux-audit@redhat.com
List-Id: linux-audit@redhat.com

Hello,

When I run across a seccomp event, does it always mean that the syscall 
failed? Is there any possibility that the syscall may have continued (such as 
while being traced)?

-Steve