On Fri, Apr 6, 2012 at 4:26 PM, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote: > On Thu, 29 Mar 2012 15:02:00 -0500 > Will Drewry <wad@xxxxxxxxxxxx> wrote: > >> Documents how system call filtering using Berkeley Packet >> Filter programs works and how it may be used. >> Includes an example for x86 and a semi-generic >> example using a macro-based code generator. >> >> >> ... >> >> +Adding architecture support >> +----------------------- >> + >> +See arch/Kconfig for the authoritative requirements. In general, if an >> +architecture supports both ptrace_event and seccomp, it will be able to >> +support seccomp filter with minor fixup: SIGSYS support and seccomp return >> +value checking. Then it must just add CONFIG_HAVE_ARCH_SECCOMP_FILTER >> +to its arch-specific Kconfig. >> diff --git a/samples/Makefile b/samples/Makefile >> index 2f75851..5ef08bb 100644 >> --- a/samples/Makefile >> +++ b/samples/Makefile > > Oh good, I was going to ask about that. > > Can we get this code into tools/testing/selftests? That way people > will run it more often and it's more likely to be maintained as the > code evolves. I'm currently using a lightweight testsuite in addition to the samples. It's a little more oriented at pass/fail behavior. Would it be more appropriate to post those in addition to, or instead of, samples? thanks! -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
