CHROMIUM: arch/arm: move secure_computing into trace; respect return code
authorWill Drewry <wad@chromium.org>
Mon, 16 Apr 2012 21:37:17 +0000 (16:37 -0500)
committerGrant Grundler <grundler@google.com>
Thu, 24 May 2012 22:16:48 +0000 (15:16 -0700)
commit5ea62181f0366d29b373b714c203bfcb9127048d
tree4edbb3b23adbb50d188b748357b92615b093b793
parent43520a3be4bfcf943d64c30f5f84f3fed55ab25d
CHROMIUM: arch/arm: move secure_computing into trace; respect return code

There is very little difference in the TIF_SECCOMP and TIF_SYSCALL_TRACE
patsh in entry-common.S. In order to add support for
CONFIG_HAVE_ARCH_SECCOMP_FILTER without mangling the assembly too
badly, seccomp was moved into the syscall_trace() handler.

Additionally, the return value for secure_computing() is now checked
and a -1 value will result in the system call being skipped.

(Reworked for 3.4 merge to just piggyback on the audit enter path.)

Signed-off-by: Will Drewry <wad@chromium.org>
BUG=chromium-os:27878
TEST=compiles for arm. Need to test on a live machine.

Change-Id: I9493f28c30356a10eccb320e0a2d1a141388af9a
Reviewed-on: https://gerrit.chromium.org/gerrit/21376
Reviewed-by: Will Drewry <wad@chromium.org>
Tested-by: Will Drewry <wad@chromium.org>
arch/arm/kernel/entry-common.S
arch/arm/kernel/ptrace.c