* [PATCH]: Set CONFIG_SECCOMP default to 'n'
@ 2005-03-25 3:25 Kumba
0 siblings, 0 replies; only message in thread
From: Kumba @ 2005-03-25 3:25 UTC (permalink / raw)
To: Linux MIPS List; +Cc: Ralf Baechle
[-- Attachment #1: Type: text/plain, Size: 383 bytes --]
As I recently learned, CONFIG_SECCOMP's default value is "y", and this can
cause the build to fail until the remaining bits of this feature are
committed. The attached patch changes the default to "n".
--Kumba
--
"Such is oft the course of deeds that move the wheels of the world: small
hands do them because they must, while the eyes of the great are elsewhere."
--Elrond
[-- Attachment #2: misc-2.6.12-seccomp-no-default.patch --]
[-- Type: text/plain, Size: 431 bytes --]
--- arch/mips/Kconfig.orig 2005-03-21 14:31:08.757419840 -0500
+++ arch/mips/Kconfig 2005-03-21 14:31:20.955565440 -0500
@@ -1422,7 +1422,7 @@ config BINFMT_ELF32
config SECCOMP
bool "Enable seccomp to safely compute untrusted bytecode"
depends on PROC_FS && BROKEN
- default y
+ default n
help
This kernel feature is useful for number crunching applications
that may need to compute untrusted bytecode during their
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2005-03-25 3:24 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-03-25 3:25 [PATCH]: Set CONFIG_SECCOMP default to 'n' Kumba
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.