From: Corey Bryant <coreyb@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: linux-security-module@vger.kernel.org, jmorris@namei.org,
wad@chromium.org, pmoore@redhat.com, otubo@linux.vnet.ibm.com
Subject: [PATCH v2 2/3] Documentation: SECCOMP_RET_INFO return value
Date: Mon, 7 Jan 2013 12:09:04 -0500 [thread overview]
Message-ID: <1357578545-2396-2-git-send-email-coreyb@linux.vnet.ibm.com> (raw)
In-Reply-To: <1357578545-2396-1-git-send-email-coreyb@linux.vnet.ibm.com>
Adds documentation describing the SECCOMP_RET_INFO return value.
Signed-off-by: Corey Bryant <coreyb@linux.vnet.ibm.com>
---
v2:
- Add arch to message (wad@chromium.org)
Documentation/prctl/seccomp_filter.txt | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/Documentation/prctl/seccomp_filter.txt b/Documentation/prctl/seccomp_filter.txt
index 1e469ef..88d6882 100644
--- a/Documentation/prctl/seccomp_filter.txt
+++ b/Documentation/prctl/seccomp_filter.txt
@@ -49,6 +49,7 @@ CONFIG_HAVE_ARCH_SECCOMP_FILTER, then filters may be added as below:
PR_SET_SECCOMP:
Now takes an additional argument which specifies a new filter
using a BPF program.
+
The BPF program will be executed over struct seccomp_data
reflecting the system call number, arguments, and other
metadata. The BPF program must then return one of the
@@ -138,6 +139,13 @@ SECCOMP_RET_TRACE:
allow use of ptrace, even of other sandboxed processes, without
extreme care; ptracers can use this mechanism to escape.)
+SECCOMP_RET_INFO:
+ Results in a rate-limited informational kernel message that
+ includes the system call number and architecture, and the
+ system call is executed. The message format is:
+ "seccomp: syscall=x, arch=y", where x is the system call number
+ and y is the architecture.
+
SECCOMP_RET_ALLOW:
Results in the system call being executed.
--
1.7.11.7
next prev parent reply other threads:[~2013-01-07 17:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 17:09 [PATCH v2 1/3] seccomp: Add SECCOMP_RET_INFO return value Corey Bryant
2013-01-07 17:09 ` Corey Bryant [this message]
2013-01-07 17:09 ` [PATCH v2 3/3] samples: Add sample using SECCOMP_RET_INFO Corey Bryant
2013-01-14 21:45 ` [PATCH v2 1/3] seccomp: Add SECCOMP_RET_INFO return value Paul Moore
2013-01-14 21:50 ` Corey Bryant
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1357578545-2396-2-git-send-email-coreyb@linux.vnet.ibm.com \
--to=coreyb@linux.vnet.ibm.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=otubo@linux.vnet.ibm.com \
--cc=pmoore@redhat.com \
--cc=wad@chromium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox