Signed-off-by: Andy Lutomirski <[email protected]>
---
Sorry for the huge delay -- I had somehow convinced myself that I'd
already done this.
Changes from v1: Tweaked the ERRNO text.
src/python/seccomp.pyx | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/src/python/seccomp.pyx b/src/python/seccomp.pyx
index 47d2ae1..396c31d 100644
--- a/src/python/seccomp.pyx
+++ b/src/python/seccomp.pyx
@@ -79,8 +79,16 @@ KILL = libseccomp.SCMP_ACT_KILL
TRAP = libseccomp.SCMP_ACT_TRAP
ALLOW = libseccomp.SCMP_ACT_ALLOW
def ERRNO(int errno):
+ """The action ERRNO(x) means that the syscall will return (x).
+ To conform to Linux syscall calling conventions, the syscall return
+ value should almost always be a negative number.
+ """
return libseccomp.SCMP_ACT_ERRNO(errno)
def TRACE(int value):
+ """The action TRACE(x) means that, if the process is being traced, (x)
+ will be returned to the tracing process via PTRACE_EVENT_SECCOMP
+ and the PTRACE_GETEVENTMSG option.
+ """
return libseccomp.SCMP_ACT_TRACE(value)
NE = libseccomp.SCMP_CMP_NE
--
1.8.3.1
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
libseccomp-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libseccomp-discuss
