Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757180Ab1D1Wy6 (ORCPT ); Thu, 28 Apr 2011 18:54:58 -0400 Received: from tundra.namei.org ([65.99.196.166]:49073 "EHLO tundra.namei.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752531Ab1D1Wy5 (ORCPT ); Thu, 28 Apr 2011 18:54:57 -0400 Date: Fri, 29 Apr 2011 08:54:26 +1000 (EST) From: James Morris To: Will Drewry cc: KOSAKI Motohiro , linux-kernel@vger.kernel.org, kees.cook@canonical.com, eparis@redhat.com, agl@chromium.org, mingo@elte.hu, rostedt@goodmis.org, Andrew Morton , Alexey Dobriyan , David Howells , Al Viro , David Rientjes , Stephen Wilson Subject: Re: [PATCH 4/7] seccomp_filter: add process state reporting In-Reply-To: Message-ID: References: <1303960136-14298-1-git-send-email-wad@chromium.org> <1303960136-14298-3-git-send-email-wad@chromium.org> <20110428122334.D197.A69D9226@jp.fujitsu.com> User-Agent: Alpine 2.00 (LRH 1167 2008-08-23) 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 Content-Length: 563 Lines: 19 On Wed, 27 Apr 2011, Will Drewry wrote: > > Can't you make individual seccomp specific file? > > Definitely. Would it make sense to have /proc//seccomp and > /proc//seccomp_filter? Do you need the separate seccomp file vs. just checking what's in seccomp_filter ? -- James Morris -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/