From 38f9fa7fa8499cffc037656c8b8bf31bad7e67ed Mon Sep 17 00:00:00 2001 From: Tudor Brindus Date: Thu, 25 Jun 2020 16:54:04 -0400 Subject: [PATCH] doc: clarify seccomp_rule_add syscall translation behavior Refs #259. Signed-off-by: Tudor Brindus --- doc/man/man3/seccomp_rule_add.3 | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/doc/man/man3/seccomp_rule_add.3 b/doc/man/man3/seccomp_rule_add.3 index 99d85e25..017e8140 100644 --- a/doc/man/man3/seccomp_rule_add.3 +++ b/doc/man/man3/seccomp_rule_add.3 @@ -147,7 +147,10 @@ value directly using the standard values, in order to ensure proper operation across multiple architectures it is highly recommended to use the .BR SCMP_SYS () -macro instead. See the EXAMPLES section below. +macro instead. See the EXAMPLES section below. If using +.B __NR_syscall +values in a multi-architecture filter, the syscall corresponding to the value +in the native architecture will be used in all non-native architectures. .P Starting with Linux v4.8, there may be a need to create a rule with a syscall value of -1 to allow tracing programs to skip a syscall invocation; in order