|
@@ -32,6 +32,7 @@ config TILE
|
|
select EDAC_SUPPORT
|
|
select EDAC_SUPPORT
|
|
select GENERIC_STRNCPY_FROM_USER
|
|
select GENERIC_STRNCPY_FROM_USER
|
|
select GENERIC_STRNLEN_USER
|
|
select GENERIC_STRNLEN_USER
|
|
|
|
+ select HAVE_ARCH_SECCOMP_FILTER
|
|
|
|
|
|
# FIXME: investigate whether we need/want these options.
|
|
# FIXME: investigate whether we need/want these options.
|
|
# select HAVE_IOREMAP_PROT
|
|
# select HAVE_IOREMAP_PROT
|
|
@@ -221,6 +222,22 @@ config COMPAT
|
|
If enabled, the kernel will support running TILE-Gx binaries
|
|
If enabled, the kernel will support running TILE-Gx binaries
|
|
that were built with the -m32 option.
|
|
that were built with the -m32 option.
|
|
|
|
|
|
|
|
+config SECCOMP
|
|
|
|
+ bool "Enable seccomp to safely compute untrusted bytecode"
|
|
|
|
+ depends on PROC_FS
|
|
|
|
+ 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, it cannot be disabled and the task is only
|
|
|
|
+ allowed to execute a few safe syscalls defined by each seccomp
|
|
|
|
+ mode.
|
|
|
|
+
|
|
|
|
+ If unsure, say N.
|
|
|
|
+
|
|
config SYSVIPC_COMPAT
|
|
config SYSVIPC_COMPAT
|
|
def_bool y
|
|
def_bool y
|
|
depends on COMPAT && SYSVIPC
|
|
depends on COMPAT && SYSVIPC
|