From mboxrd@z Thu Jan  1 00:00:00 1970
From: Dave Hansen <dave@sr71.net>
Subject: Re: [PATCH 1/3] kconfig: consolidate arch-specific seccomp options
Date: Sat, 04 Jan 2014 11:04:20 -0800
Message-ID: <52C85B34.6040001@sr71.net>
References: <20140102202014.CA206E9B@viggo.jf.intel.com> <20140105023853.dda6c1f9c6f9875159634e69@canb.auug.org.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Return-path: <linux-arch-owner@vger.kernel.org>
Received: from www.sr71.net ([198.145.64.142]:35335 "EHLO blackbird.sr71.net"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1754120AbaADTE2 (ORCPT <rfc822;linux-arch@vger.kernel.org>);
	Sat, 4 Jan 2014 14:04:28 -0500
In-Reply-To: <20140105023853.dda6c1f9c6f9875159634e69@canb.auug.org.au>
Sender: linux-arch-owner@vger.kernel.org
List-ID: <linux-arch.vger.kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-kernel@vger.kernel.org, linux-security-module@vger.kernel.org, linux-arch@vger.kernel.org

On 01/04/2014 07:38 AM, Stephen Rothwell wrote:
> On Thu, 02 Jan 2014 12:20:14 -0800 Dave Hansen <dave@sr71.net> wrote:
>> From: Dave Hansen <dave.hansen@linux.intel.com>
>> There is *NOTHING* architecture-specific about SECCOMP except
>> that the syscalls have per-architecture definitions, like every
>> other syscall.  It is absurd to have the option in the
>> arch-specific menus.
> 
> You seem to have (mostly) lost the dependency some of the architecture
> versions of config SECCOMP had on PROC_FS ...

I _believe_ the /proc interface has gone away.  I can't find any
reference to /proc/<pid>/seccomp in any of the code.  Is there some
/proc dependency that I'm missing outside of the removed
/proc/<pid>/seccomp interface?