[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110428174334.GB25940@hallyn.com>
Date: Thu, 28 Apr 2011 12:43:34 -0500
From: "Serge E. Hallyn" <serge@...lyn.com>
To: Ingo Molnar <mingo@...e.hu>
Cc: Will Drewry <wad@...omium.org>, linux-kernel@...r.kernel.org,
kees.cook@...onical.com, eparis@...hat.com, agl@...omium.org,
jmorris@...ei.org, rostedt@...dmis.org,
Randy Dunlap <rdunlap@...otime.net>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Tom Zanussi <tzanussi@...il.com>,
Frédéric Weisbecker <fweisbec@...il.com>,
Arnaldo Carvalho de Melo <acme@...hat.com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH 5/7] seccomp_filter: Document what seccomp_filter is and
how it works.
Quoting Ingo Molnar (mingo@...e.hu):
> I've Cc:-ed Linus and Andrew: are you guys opposed to such flexible, dynamic
> filters conceptually? I think we should really think hard about the actual ABI
> as this could easily spread to more applications than Chrome/Chromium.
We want to use it for containers, to try and provide some bit of
mitigation for the fact that they are sharing a kernel with the host.
thanks,
-serge
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists