Candidate replacement approach for seccomp_filter (no ftrace)

[Andy Whitcroft]

On Fri, Jan 27, 2012 at 10:35:23AM -0600, Will Drewry wrote:

> Looking at the oops, it appears to be in ftrace filter creation.  It's
> possible that ftrace changes its internals in the middle of that
> kernel roll and create_preds is walking off into space.  I can take a
> look, if needed - let me know.

So are the old and new patch sets semantically equivalent to the seccomp
consumer?  At the time we took the previous patch set I seem to remember
it was to enable seccomp use by the chromium-browser.  Is that going to
work with the new patch set?

-apw