[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LRH.2.00.1108150927210.31525@tundra.namei.org>
Date: Mon, 15 Aug 2011 09:29:18 +1000 (EST)
From: James Morris <jmorris@...ei.org>
To: "H. Peter Anvin" <hpa@...or.com>
cc: Andi Kleen <andi@...stfloor.org>, Solar Designer <solar@...nwall.com>,
Vasiliy Kulikov <segoon@...nwall.com>,
Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>,
kernel-hardening@...ts.openwall.com, x86@...nel.org,
linux-kernel@...r.kernel.org, linux-security-module@...r.kernel.org,
Will Drewry <wad@...omium.org>
Subject: Re: [RFC] x86: restrict pid namespaces to 32 or 64 bit syscalls
On Sun, 14 Aug 2011, H. Peter Anvin wrote:
> Last I looked seccomp still had a hardcoded list of system calls, but
> perhaps I've been looking in the wrong place. However, since that's
> exactly what seccomp is -- a system call filter -- this can, and should,
> be unified that way.
Yes, we should definitely look at incorporating this into seccomp v2,
which is still under discussion (and a topic at KS).
- James
--
James Morris
<jmorris@...ei.org>
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
