Skip to content

Commit

Permalink
---
Browse files Browse the repository at this point in the history
yaml
---
r: 110373
b: refs/heads/master
c: 9c0bbee
h: refs/heads/master
i:
  110371: 8bb63e0
v: v3
  • Loading branch information
Alexey Dobriyan authored and Ingo Molnar committed Sep 9, 2008
1 parent d5579b9 commit ce2cb6e
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 3 deletions.
2 changes: 1 addition & 1 deletion [refs]
Original file line number Diff line number Diff line change
@@ -1,2 +1,2 @@
---
refs/heads/master: afe73824f52d6767c77e9456f573a76075108279
refs/heads/master: 9c0bbee8a6fc14107e9a7af6750bfe1056cbf4bc
3 changes: 1 addition & 2 deletions trunk/arch/x86/Kconfig
Original file line number Diff line number Diff line change
Expand Up @@ -1205,15 +1205,14 @@ config IRQBALANCE
config SECCOMP
def_bool y
prompt "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 /proc/<pid>/seccomp, it cannot be disabled
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.

Expand Down

0 comments on commit ce2cb6e

Please sign in to comment.