Branch: refs/heads/master
Home: https://github.com/seccomp/libseccomp
Commit: bf162816a6e42d7a40e54aadc18d1a98c34ca971
https://github.com/seccomp/libseccomp/commit/bf162816a6e42d7a40e54aadc18d1a98c34ca971
Author: Paul Moore <[email protected]>
Date: 2019-10-01 (Tue, 01 Oct 2019)
Changed paths:
A include/seccomp-syscalls.h
M include/seccomp.h.in
M tools/check-syntax
Log Message:
-----------
api: stop defining __NR_x values for syscalls that don't exist
Historically libseccomp has created a __NR_x definition for every
syscall it supports, even those that aren't valid for a given ABI.
While this seemed like a good idea at the time, it turned out to have
some unwanted and nasty side effects. This patch finally corrects
this problem.
The basic approach is quite simple: move the SCMP_SYS() macro to use
__SNR_x values instead of __NR_x values. The unfortunate side effect
of this change is that instead of just worrying about #defines for the
__PNR_x values we now have to have a __SNR_x define for *every*
syscall. The good news is that after this patch that should only be
a few new syscalls every year - a very manageable task.
Reviewed-by: Tom Hromatka <[email protected]>
Signed-off-by: Paul Moore <[email protected]>
--
You received this message because you are subscribed to the Google Groups
"libseccomp" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/libseccomp/seccomp/libseccomp/push/refs/heads/master/853a24-bf1628%40github.com.
