|
@@ -38,6 +38,7 @@ config ARM64
|
|
|
select HAVE_ARCH_AUDITSYSCALL
|
|
|
select HAVE_ARCH_JUMP_LABEL
|
|
|
select HAVE_ARCH_KGDB
|
|
|
+ select HAVE_ARCH_SECCOMP_FILTER
|
|
|
select HAVE_ARCH_TRACEHOOK
|
|
|
select HAVE_BPF_JIT
|
|
|
select HAVE_C_RECORDMCOUNT
|
|
@@ -455,6 +456,19 @@ config ARCH_HAS_CACHE_LINE_SIZE
|
|
|
|
|
|
source "mm/Kconfig"
|
|
|
|
|
|
+config SECCOMP
|
|
|
+ bool "Enable seccomp to safely compute untrusted bytecode"
|
|
|
+ ---help---
|
|
|
+ This kernel feature is useful for number crunching applications
|
|
|
+ that may need to compute untrusted bytecode during their
|
|
|
+ execution. By using pipes or other transports made available to
|
|
|
+ the process as file descriptors supporting the read/write
|
|
|
+ syscalls, it's possible to isolate those applications in
|
|
|
+ their own address space using seccomp. Once seccomp is
|
|
|
+ enabled via prctl(PR_SET_SECCOMP), it cannot be disabled
|
|
|
+ and the task is only allowed to execute a few safe syscalls
|
|
|
+ defined by each seccomp mode.
|
|
|
+
|
|
|
config XEN_DOM0
|
|
|
def_bool y
|
|
|
depends on XEN
|