From 5945cd7bd3c310b4c8a6dfc1eb55c9d066a63952 Mon Sep 17 00:00:00 2001 From: Alejandro Colomar Date: Sat, 12 Jun 2021 10:31:19 +0200 Subject: [PATCH] seccomp.2: Use syscall(SYS_...); for system calls without a wrapper Signed-off-by: Alejandro Colomar Signed-off-by: Michael Kerrisk --- man2/seccomp.2 | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/man2/seccomp.2 b/man2/seccomp.2 index 53f473a788..a3421871f0 100644 --- a/man2/seccomp.2 +++ b/man2/seccomp.2 @@ -38,13 +38,18 @@ seccomp \- operate on Secure Computing state of the process .BR "#include " " /* Definition of " PTRACE_* " constants */" .\" Kees Cook noted: Anything that uses SECCOMP_RET_TRACE returns will .\" need +.BR "#include " " /* Definition of " SYS_* " constants */" +.B #include .PP -.BI "int seccomp(unsigned int " operation ", unsigned int " flags \ -", void *" args ); +.BI "int syscall(SYS_seccomp, unsigned int " operation ", unsigned int " flags , +.BI " void *" args ); .fi .PP .IR Note : -There is no glibc wrapper for this system call; see NOTES. +glibc provides no wrapper for +.BR seccomp (), +necessitating the use of +.BR syscall (2). .SH DESCRIPTION The .BR seccomp () @@ -930,9 +935,6 @@ Tile (since Linux 4.3) PA-RISC (since Linux 4.6) .\" User mode Linux since Linux 4.6 .PD -.PP -Glibc does not provide a wrapper for this system call; call it using -.BR syscall (2). .\" .SS Caveats There are various subtleties to consider when applying seccomp filters -- 2.47.3