Commit 6b79ecd0 authored by Masahiro Yamada's avatar Masahiro Yamada Committed by Huacai Chen
Browse files

LoongArch: Select HAVE_ARCH_SECCOMP to use the common SECCOMP menu 



LoongArch missed the refactoring made by commit 282a181b ("seccomp:
Move config option SECCOMP to arch/Kconfig") because LoongArch was not
mainlined at that time.

The 'depends on PROC_FS' statement is stale as described in that commit.
Select HAVE_ARCH_SECCOMP, and remove the duplicated config entry.

Signed-off-by: default avatarMasahiro Yamada <masahiroy@kernel.org>
Signed-off-by: default avatarHuacai Chen <chenhuacai@loongson.cn>
parent b3ff2d9c

arch/loongarch/Kconfig

+1 −17
Original line number Diff line number Diff line
@@ -100,6 +100,7 @@ config LOONGARCH 
	select HAVE_ARCH_KFENCE

	select HAVE_ARCH_KGDB if PERF_EVENTS

	select HAVE_ARCH_MMAP_RND_BITS if MMU

	select HAVE_ARCH_SECCOMP

	select HAVE_ARCH_SECCOMP_FILTER

	select HAVE_ARCH_TRACEHOOK

	select HAVE_ARCH_TRANSPARENT_HUGEPAGE
@@ -633,23 +634,6 @@ config RANDOMIZE_BASE_MAX_OFFSET 


	  This is limited by the size of the lower address memory, 256MB.



config SECCOMP

	bool "Enable seccomp to safely compute untrusted bytecode"

	depends on PROC_FS

	default y

	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 /proc/<pid>/seccomp, it cannot be disabled

	  and the task is only allowed to execute a few safe syscalls

	  defined by each seccomp mode.



	  If unsure, say Y. Only embedded should say N here.



endmenu



config ARCH_SELECT_MEMORY_MODEL