[Top] [All Lists]

Re: [PATCH 3/5] v2 seccomp_filters: Enable ftrace-based system call filt

Subject: Re: [PATCH 3/5] v2 seccomp_filters: Enable ftrace-based system call filtering
From: Arnd Bergmann <>
Date: Fri, 13 May 2011 21:35:34 +0200
Cc: Will Drewry <>,,,, Peter Zijlstra <>, Frederic Weisbecker <>, Heiko Carstens <>, David Howells <>, Paul Mackerras <>, Eric Paris <>, "H. Peter Anvin" <>,, Jiri Slaby <>,, Russell King <>,,, Ingo Molnar <>, Benjamin Herrenschmidt <>, Ingo Molnar <>, "Serge E. Hallyn" <>, Peter Zijlstra <>,, Steven Rostedt <>, Martin Schwidefsky <>, Thomas Gleixner <>,, Roland McGrath <>, Michal Marek <>, Michal Simek <>,, Oleg Nesterov <>, Ralf Baechle <>, Paul Mundt <>, Tejun Heo <>,, Andrew Morton <>,, "David S. Miller" <>
In-reply-to: <>
Original-recipient: rfc822;
References: <> <>
User-agent: KMail/1.12.2 (Linux/2.6.37; KDE/4.3.2; x86_64; ; )
On Thursday 12 May 2011, Will Drewry wrote:
> This change adds a new seccomp mode based on the work by
> in [1]. This new mode, "filter mode", provides a hash
> table of seccomp_filter objects.  When in the new mode (2), all system
> calls are checked against the filters - first by system call number,
> then by a filter string.  If an entry exists for a given system call and
> all filter predicates evaluate to true, then the task may proceed.
> Otherwise, the task is killed (as per seccomp_mode == 1).

I've got a question about this: Do you expect the typical usage to disallow
ioctl()? Given that ioctl alone is responsible for a huge number of exploits
in various drivers, while certain ioctls are immensely useful (FIONREAD,
FIOASYNC, ...), do you expect to extend the mechanism to filter specific
ioctl commands in the future?


<Prev in Thread] Current Thread [Next in Thread>